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 ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Add comment