Search Issue Tracker
Duplicate
Votes
0
Found in
2019.1.0a10
Issue ID
1108346
Regression
Yes
Visual Studio debugging does not work when UnityEngine.UI namespace is used together with .NET 3.5
Reproduction steps:
1. Open the attached project
2. Open the UIScript.cs
3. Inside Visual Studio Toolbar -> Attach to Unity
Expected: Visual Studio starts debugging
Actual: Visual Studio throws an error and does not start debugging
Regression first introduced on - 2019.1.0a6
Does not reproduce on: 2017.4.18f1, 2018.3.3f1, 2019.1.0a13, 2019.2.0a1
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