Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.1.6f1
Issue ID
1052839
Regression
No
Dynamically generated assemblies created with C#'s native AssemblyBuilder class cause project to break
How to reproduce:
1. Open the attached user project and reimport the "unityImportTest.cdb" asset
2. Tab out/in so the DLL (CastleDBTypesAssembly) is added to the Assets folder
3. In the Hierarchy click on the "testGameObject" and then in the Inspector Window click "Test" - observe the Console
4. Comment out the Debug line in the "CDBTest.cs: script.and then uncomment lines 17-19
5. Go back to Unity, click on the "testGameObject", click "Test", and observe the proper Debug "testing" message is still printed.
6. Make a new Monobehaviour script in the project with Create > C# Script and try to attach it to any object in the Hierarchy
Expected result: the commented out debug message no longer appears, adding new scripts works as intended
Actual result: the commented out debug message still appears in the console, adding new scripts to game objects fails
Reproduced in: 2018.2.1f1, 2018.1.9f1
Couldn't test with: 2018.3.0a5, 2017.4.6f1, 2017.2.3p2, 2017.1.5f1
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.