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
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
- Editor crashes on D3D12GetInterface when repeatedly enabling and disabling 256 text components
- Flickering bright white dots in the Scene when the Android Platform is selected and DX11 Graphics API is used with Iris(R) Xe Graphics GPU
- Inconsistent capitalization and misaligned text in multiple query blocks in Search window
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
Resolution Note:
Assembly references are missing in the included project. Newer versions of Unity (2019.2 at least) report better errors alluding to this.