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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment