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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
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.