Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.4.0f1
2018.3.0a1
2019.1.0a1
2019.1.0f2
2019.2.0a1
2019.3.0a1
Issue ID
1149266
Regression
No
Visual Studio Debugger's "Step Into" function does not work between assembly definitions
How to reproduce:
1. Open the attached project ("TestDebug.zip")
2. Open the repro scene ("SampleScene")
2. Open the "Test1.cs" script
3. Add a breakpoint on line 8
4. Press "F11" to start debugging
5. Enter the Play Mode
6. "Step Into" the constructor inside the Visual Studio
Expected results: Visual Studio steps into the constructor
Actual results: Visual Studio does not step into the constructor
Reproducible with: 2017.4.26f1, 2018.3.14f1, 2019.1.1f1, 2019.2.0a14, 2019.3.0a1
Note:
The "Step into" function works as expected when both scripts are in the same assembly definition
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
- Metal Vertex Shader warning is being thrown when creating a VR Template Project
- Asset database warning is thrown when declaring font variable in the USS text file
- Memory Leak warnings are thrown when opening an imported Prefab
- Crash on mono_push_other_roots when setting Normal Thread Affinity
- Editor exits Play mode when another project is being created using Unity Hub 3.8.0-beta.1
Resolution Note (2020.1.X):
This issue have been forwarded to the Visual Studio team that is in charge of the debugger for unity that Visual Studio uses.