Search Issue Tracker
By Design
Votes
0
Found in
2018.2.11f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1089965
Regression
No
Editor doesn't handle DLL files created with an earlier version than the one in the Json file with IL2CPP and NetStandard 2
Reproduction steps:
1. Open "NetIlRepro.zip" project
2. Enter Play mode
3. Notice Error in Console
4. Build and Run Standalone Player with "Development Build" Enabled
5. Notice no Error is displayed in the Development Console
Expected Result: Editor handles DLL files created with an earlier version than the one in the Json file properly, just as in the Standalone Player
Actual Result: Editor doesn't handle DLL files created with an earlier version than the one in the Json file with IL2CPP and NetStandard 2, but the Standalone Player does
Reproduced with: 2019.2.0a2, 2019.1.0a14, 2018.3.3f1, 2018.1.9f2
Did not reproduce on: 2017.4.19f1 (Definition error)
Error:
TypeLoadException: Could not load type of field 'Microsoft.Azure.CognitiveServices.Language.LUIS.Runtime.LUISRuntimeClient:<SerializationSettings>k__BackingField' (1) due to: Could not load file or assembly 'Newtonsoft.Json, Version=9.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. assembly:Newtonsoft.Json, Version=9.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed type:<unknown type> member:(null) signature:<none>
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
- Crash on DynamicHeapAllocator::CreateTLSFBlock when opening a specific project
- Scene flickers when using Mesh Output with SpriteLit Shader in 2D project
- “Cache Management” text is misaligned in Preferences > Package Manager
- [macOS] network permission shows the name of previously closed app when different app requests network access
- Delta value returned by mouse movementsMonitor is different when changing Screen Resolution
Resolution Note:
Newtonsoft.json provided is a strong named assembly, so the versions must match exactly. See documentation from microsoft on strong signed assemblies https://docs.microsoft.com/en-us/dotnet/framework/app-domains/strong-named-assemblies