We've just upgraded our Unity installed base from 2.6 to 3.0. When we were running 2.6, the project would build fine using our automated build system. Under 3.0 the project fails with this error:
Error building Player: Extracting referenced dlls failed. UnityEditor.HostView:OnGUI()
No new dlls have been added to the project since we were using 2.6. I found references to this problem by other people:
Anybody know what's going on here? Why did it work fine in 2.6 but not in 3.0?
We also see this error:
ArgumentException: The Assembly UnityEditor is referenced by Path. But the dll is not allowed to be included or could not be found.
UnityEditor.AssemblyHelper.AddReferencedAssembliesRecurse (System.String assemblyPath, System.Collections.Generic.List
One thing I noticed about the second error is "Path". We're using AngryAnt's Path library. Then I found this question. I think we may be on to something...
Path 1.0 is not Unity 3 compatible. I'm currently working on a 1.1 release which will address this and many other things.
Some background: Unity 2.x allowed assemblies to link to UnityEditor and still be compiled in with everything else on build time as long as it didn't try to invoke anything in UnityEditor. Unity 3 is more strict and requires a complete split between UnityEditor code and UnityEngine code.
answered Oct 14 '10 at 09:40 AM
This is most likely due to the much more restrictive handling of Mono in Unity 3. There's now different profiles and not all of the profiles support all the Mono features. In particular, Web players can only use a limited set of Mono features which might explain the behavior.
answered Oct 08 '10 at 05:55 AM
You can try to change API Compatibility Level: to .Net 2.0. choose Edit->Project Settings->Player, then follow this link http://unity3d.com/support/documentation/Components/class-PlayerSettings.html
Helped me with building..
answered Jan 17 '11 at 08:29 PM
Is anyone found solution for that. I'm experiencing same problem with UniLOD on Unity 3.1
answered Nov 25 '10 at 11:15 AM