Search Issue Tracker
Fixed in 2019.2.X
Votes
0
Found in
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1105512
Regression
No
Visual Studio continues to warn about unsafe code when unsafe code is enabled in Project Settings
How to reproduce:
1. Open the attached project ("case-1105512-Unsafe Code.zip")
2. Notice the error regarding "unsafe code" in the console
3. Open the script ("UnsafeTest.cs") using Visual Studio
4. Notice that Visual Studio is giving warnings regarding the unsafe method
5. In the Editor, enable unsafe code (Edit -> Project Settings -> Player)
6. Notice that there aren't any errors in the console anymore
7. Go back to the Visual Studio and inspect the unsafe method
Expected results: Visual Studio no longer warns about the unsafe code
Actual results: Visual Studio continues to warn about the unsafe code
Reproducible with: 2018.3.9f1, 2019.1.0b7, 2019.2.0a8
Couldn't reproduce on 2017.4, because it doesn't allow to enable unsafe code via Project Settings
Notes:
1. Re-opening Visual Studio fixes the issue.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Default and Result encoding properties have blank dropdowns by default when opening the Unity Version Control Settings
- Crash on "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
- Warnings due to obsolete Object.FindObjectsByType<T> usage and [SerializeReference] are logged when opening the Netcode for Entities setup scene
- Non-standard pointers cannot change Inspector values with arrow controls when crossing Inspector area
Resolution Note (fix version 2019.2):
Fixed in 2019.3.0a1
Backported to 2019.2.0a15