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
- Some post-processing volume overrides only update after a refresh when using HDRP
- Video Player glitches when Skip On Drop is enabled
- GameObject movement in Scene view becomes stuttery and intermittently freezes when using non-standard pointers across editor tabs or window boundaries
- Addressables.CheckForCatalogUpdates() always returns 0 when "Only update catalogs manually" is enabled
- VFX Graph forces a lengthy recompilation freeze when exiting Play Mode with a cloned Render Pipeline asset
Resolution Note (fix version 2019.2):
Fixed in 2019.3.0a1
Backported to 2019.2.0a15