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
- Crash on PluginManager::RefreshPlugins when closing the Editor without making any changes with JetBrains Rider selected as the External Code Editor and Google Mobile Ads third-party plugin imported
- GetMainLight() returns incorrect distanceAttenuation value for a Custom Shader when URP Forward+ Rendering Path is used
- Standalone Profiler crash on GuidReservations::Reserve when it is opened on a specific project
- m_RenderPipelineGlobalSettingsMap or m_SRPDefaultSettings is pointing to UnityEngine.Rendering.HighDefinition.HDRenderPipeline when High Definition RP package is removed
- Rendering Debugger fields have no padding at the bottom of the fields list
Add comment