Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2020.1.2f1
2020.2
Issue ID
1272620
Regression
No
csproj's are not generated when there's an invalid or incompatible define constraint in the asmdef
How to reproduce:
1. Open the attached project
2. Open the Unity project's solution file
3. Inspect Scripts in the IDE
Expected result: csproj's are generated when there's an invalid or incompatible define constraint in the asmdef
Actual result: csproj's are not generated when there's an invalid or incompatible define constraint in the asmdef
Reproducible with: 2018.4.26f1, 2019.4.9f1, 2020.1.4f1, 2020.2.0b1
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
- [Remote Config] PreparePayloadWithConfigType function is looking for camelCase property names, when the JSON objects are using PascalCase naming
- UI Builder Viewport's Tool Gizmo has deadzones
- SpriteShapes are rendered using multiple draw calls when the SRP Batcher determines their nodes are incompatible in a specific project
- UI Toolkit Debugger "Pick Element" selects Scene view panel when trying to select a world space UI element in the Scene view
- MSAA warnings are thrown when custom post-processing is used and the Scene contains transparent GameObjects
Resolution Note:
Generating Visual Studio Projects unconditionally could lead to projects failing to compile in Visual Studio (because users use define constraints as they would use #ifdef applied for a whole directory). That is why we won't fix this one.