Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.0f3
Issue ID
994351
Regression
No
UNITY_DEVELOPMENT not working in UWP .Net build
How to reproduce:
1. Download attached project file
2. Change platform to UWP and backend to .Net
3. In Build Settings check Unity "C# project" and "Development build"
4. Build
5. Open and Build Visual Studio solution
Actual result: In Visual Studio, the Conditional Compilations list for the Project's Project Properties does not have the UNITY_DEVELOPMENT flag set.
Reproduced with:2017.1.3p3, 2017.2.2p3, 2017.4.1f1, 2018.1.0f1
Unable to test on 2018.2.0b9, because of an issue with "C# project" checkmark and TextmeshPro
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
- Inconsistent hotkeys in the Terrain tool with the "Terrain Tools" installed and not installed
Add comment