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
- Crash on UnityPlayer!profiling::ProfilerManager::DisposeProfilerRecorder+0xa when Player gets relaunched and exited after running for a long amount of time
- [Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
- Root motion is not reapplied when transitioning from an animation without root motion to an animation with root motion
Add comment