Search Issue Tracker
Won't Fix
Votes
3
Found in
2017.4.0f1
2019.2.0a11
2019.3.0a1
2019.3.0a7
Issue ID
1166748
Regression
Yes
Code completion does not work for MonoBehavior callback methods when using Visual Studio 2019
How to reproduce:
1. Create and open a new project
2. Make sure you have Visual Studio 2019 selected under Preferences > External Tools > External Script Editor
2. Create and open a new C# script
3. Try typing the beginning of any callback method (f.e. OnTriggerEnter)
Expected results: MonoBehavior callback methods appear in the suggestions
Actual results: No MonoBehavior callback methods appear in the suggestions
Reproducible with: 2017.4.29f1, 2019.2.0b8, 2019.3.0a8
Not reproducible with: 2018.4.3f1, 2019.1.8f1
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Resolution Note:
This is an issue with the Visual Studio Tools for Unity (VSTU) integration in Visual Studio 2019. We are unable to fix this bug, as this product is owned and maintained by Microsoft. Please report this bug to vstusp@microsoft.com