Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.6.0b2
Issue ID
860773
Regression
No
[UWP] Project fails to compile when using legacy classes
The easiest way to reproduce is to have a PC with only VS2017 installed
Reproduction steps:
1. Open the attached project
2. Try to build to UWP
3. Builds as expected
4. Try to build to SDK 8.1
5. Compilation will fail because only VS2017 is installed
6. Now switch back and try to build to UWP once again
7. Fails with following output (from Editor.log):
(Filename: /Users/builduser/buildslave/mono/build/mcs/class/corlib/System.IO/Directory.cs Line: 514)
- Finished compile Library/ScriptAssemblies/Assembly-CSharp.dll
Compilation failed because the compiler couldn't be executed!
(Filename: Line: 21)
DisplayProgressNotification: Build Failed
Error building Player because scripts had compiler errors
Notes:
- Sometimes not reproducible and everything works as expected, but fails in 90% of cases.
- If you remove "ArrayList" from the script in the project - everything works fine.
- Workaround: Re-import all
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Errors are logged when importing an asset at a path with Firebase
- Entering too big of a number in 2D Renderer Lightmode Tags freezes the Editor
- Crash on GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
Add comment