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
- Addressables.CheckForCatalogUpdates() always returns 0 when "Only update catalogs manually" is enabled
- VFX Graph forces a lengthy recompilation freeze when exiting Play Mode with a cloned Render Pipeline asset
- Project Auditor's "Install Rules" button has to be pressed twice to proceed when any compilation error in the Editor is present
- Crash on Scripting::UnityEngine::SubsystemManagerProxy::ClearSubsystems when adding a Mesh Collider Component to a GameObject
- ScrollView clips content when under an ancestor that has a filter set
Add comment