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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment