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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Assembly references are missing in the included project. Newer versions of Unity (2019.2 at least) report better errors alluding to this.