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
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
- Scene view has Y coordinates of the Screen Position node flipped when some of the URP features are disabled
- Volumetric fog shader variants are missing from build when "Strict Shader Variant Matching" is disabled
- Unnecessary modifications clutter the Scene when using a RectTransform driven by a LayoutGroup in a Prefab
- Files in the target folder are deleted without a proper warning when building an iOS project
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.