Search Issue Tracker
By Design
Votes
2
Found in
2018.2.0b4
Issue ID
1045941
Regression
No
"Loading script assembly ... failed!" errors when importing "Microsoft.CodeAnalysis.CSharp.Scripting"
Reproduction steps:
1. Open "RoslynTest.zip" project
2. Look at the Console window
Expected Result: No errors should be present from importing
Actual Result: importing "Microsoft.CodeAnalysis.CSharp.Scripting" causes Script Assembly errors
Reproduced with: 2018.3.0a1, 2018.2.0b7, 2018.1.4f1, 2018.1.0a1, 2017.4.5f1, 2017.3.2f1, 2017.2.3f1, 2017.1.4p1
Note:
Loading script assembly "Assets/PublishedFromVisualStudio/System.IO.Compression.dll" failed!
Loading script assembly "Assets/PublishedFromVisualStudio/System.Text.Encoding.CodePages.dll" failed!
Delete "SyntaxParseTest.cs" to repro with 2017.4 and lower
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
Assembly references are missing in the included project. Newer versions of Unity (2019.2 at least) report better errors alluding to this.