Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
5.6.0b4
Issue ID
875057
Regression
No
Custom global defines in mcs.rsp file aren't available in Visual Studio
Steps to reproduce:
1. Open the project
2. Notice there are no compiler errors
3. Open NewBehaviourScript.cs with Visual Studio
4. Notice that the custom define is grayed out
Expected: Custom define from mcs.rsp file is unrecognized by Visual Studio
Actual: Custom define from mcs.rsp is recognized by Visual Studio
Reproduced on: 5.4.4p4, 5.5.2p1, 5.6.0b9
Software used: Visual Studio Community 2015 Version 14.0.25431.01 Update 3
Note: mcs.rsp should be renamed to smcs.rcp in versions below 5.5
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
youngkyun
Jul 03, 2017 13:08
no need to compile in visual studio.
changing your c# code and click in Unity editor (will compile automatically) then
there is no problem to run unity editor.