Search Issue Tracker
Duplicate
Votes
0
Found in
2018.1.0b1
2018.1.0b3
Issue ID
990268
Regression
Yes
MonoBehaviour methods are not recognized in Visual Studio 15.5.4 because C# scripts are part of Assembly-CSharp project
Reproduction steps:
1. Open Unity and create new project
2. Create new C# script
3. Open and edit C# script and close it
4. Enable Play mode
5. Open the C# script
Expected: the script should be part of the project and writing MonoBehaviour method name ("update", "awake"...) should autocomplete/suggest code
Actual: the script is part of "Assembly-CSharp" and MonoBehaviour method names are not autocompleted/suggested
Reproduced on: 2018.1.0b1; 2018.1.0b5; 2018.2.0a1
Not reproduced on: 2017.3.1f1; 2018.1.0a7
Regression introduced: 2018.1.0b1
Note: reproduced only with Visual Studio 15.5.4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Add comment