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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment