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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
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.