Search Issue Tracker
By Design
Votes
0
Found in
2018.1.0f1
Issue ID
1032070
Regression
No
Assembly Definition files do not recompile when importing Asset Packages
Steps to reproduce:
1. Open an empty project
2. Import user-attached package "MRTK-Test.unitypackage" (rmb in Projects panel->Import Package->Custom Package)
3. See errors in the Console
Reproduced with: 2018.1.4f1, 2018.2.0b9, 2018.3.0a3
Expected result: Assembly Definitions are compiled successfully and thus the user gets a prompt to switch to .NET4.X
Actual result: Assembly Definitions are not compiled successfully and the user only gets to see API incompatibility errors in the Console. Reloading the project makes the prompt appear as intended
This behavior is assumed to be incorrect in accordance with what is written in the Release Notes of Unity 2018.1:
Editor: Unity now compiles Assembly Definition File (asmdef) assemblies on startup, before any other scripts (such as Assembly-CSharp.dll), and does not stop compilation on the first compile error. Uniy loads all asmdef assemblies that succesfully compile and have all their references compiled, then compiles the remaining scripts (Assembly-CSharp.dll and friends). This ensures that Unity packages are always built and and loaded, regardless of other compile errors in the Project.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ConvertBufferToEXRBuffer when Lighting Generation is cancelled
- [URP] TrailEffect in URP package samples does not draw Trail Effect
- "NullReferenceException" error is thrown when calling UIDocument.runtimePanel in OnEnable with ExecuteInEditMode
- Graphics.Blit() performs the operation only to the last display when a multi-display environment is used
- [Windows] Multiple Separation Lines are present in the Light Create Menu
Add comment