Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.1p2
Issue ID
944496
Regression
No
[macOS] Unable to debug managed DLL using Visual Studio for Mac
Visual Studio for Mac can't debug DLL code. Debug works as expected on non-DLL scripts.
Visual Studio can debug DLLs on Windows as expected.
Steps to reproduce:
1. Open user's attached project (132701.zip) and also extract MyDll3.zip somewhere in computer
2. Unity Preferences > External tools > External Script Editor > Visual Studio
3. Open Aasets/Test.cs
4. In VS: right click on "case_944496-132701" in Solution tab > Add > Add Existing project > navigate to MyDll3/MyDll3/MyDll.csproject
5. right click on "MyDll3" in Solution tab > Options > Output > Output pat > Set to case_944496-132701/Assets folder
6. Add a breakpoint in MyClass.cs line 13
7. Attach to Unity and Play, enter Play mode in Unity
Expected behaviour: debugger stops at the breakpoint.
Actual behaviour: debugger doesn't reach the breakpoint and doesn't stop.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Profiler connects to a different opened Editor project when more than one project is open and building for WebGL with Autoconnect Profiler enabled
- Creating and then deleting the "Integration Update: Rotation" block breaks and makes unusable VFX Graph
- “ArgumentNullException: Value cannot be null.” when deleting a newly created input action
- Undoing the creation of the "Button - TextMeshPro" GameObject only removes Canvas and EventSystem GameObjects
- NullReferenceException errors are thrown when entering the Play Mode when ShaderGraph window is focused
Add comment