Search Issue Tracker
Fixed in 5.0.X
Votes
2
Found in
4.5.0f6
Issue ID
613922
Regression
No
Incorrect conditional compilation symbols when building project with "Unity C# projects"
Building a Windows Store App project with "Unity C# Projects" option checked, results in projects are being created with the wrong Unity version in the conditional compilation symbols, for example:
<DefineConstants>...UNITY_4_0_0;UNITY_4_0;...</DefineConstants>
Repro steps:
1. Create an empty project and build a Windows Store App with the Unity C# Project checkbox ticked;
2. Examine the Conditional compilation symbols for Assembly-CSharp-metro-vs2013 and Assembly-CSharp-firstpass-metro-vs2013 projects in Unity project folder;
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture Map Viewer shows "Loading..." text instead of indicating users that Baked Texture Maps are missing
- "Analyze Import Process" button misaligned in Import Activity window
- Text in “Baked Shadowmask” mode is difficult to read in Baked Lightmap Viewer when Editor theme is set to Light
- Mesh wireframe is difficult to see in Baked Lightmap Viewer window when texture opacity is maximized
- Informational text does not wrap and does not fit when the Viewer Window is opened by default
Add comment