22 lines
1.4 KiB
Markdown
22 lines
1.4 KiB
Markdown
|
# Applications targeting .NET 4.6.1 that use .NET Standard libraries might be broken when running on .NET 4.7.1
|
||
|
|
|
||
|
|
## Symptoms
|
||
|
|
|
||
|
|
Applications that target the .NET Framework 4.6.1 and use .NET Standard libraries may experience <xref:System.TypeLoadExceptions> exceptions when running on the .NET Framework 4.7.1
|
||
|
|
|
||
|
|
## Cause
|
||
|
|
|
||
|
|
The .NET Framework 4.7.1 adds support for .NET Standard in-box. As part of this change, a few assemblies that used to ship independently from the .NET Framework have now been added to the .NET Framework. As these .NET Standard assemblies were not part of the .NET Framework prior to .NET 4.7.1, they were deployed with the application, and a binding redirect was added to the application's app.config file.
|
||
|
|
|
||
|
|
When running on the .NET Framework 4.7.1, where the assemblies are now part of the Framework, the application now has two types with different identities, and that leads to a <xref:TypeLoadException>. One type comes from the app-local assembly, and the other one comes from the .NET Framework assembly.
|
||
|
|
|
||
|
|
Also reported here: https://github.com/Microsoft/dotnet-framework-early-access/issues/9
|
||
|
|
|
||
|
|
|
||
|
|
## Workarounds
|
||
|
|
|
||
|
|
There are two ways to work around this issue:
|
||
|
|
- When running on .NET Framework 4.7.1, remove the binding redirects from the app.config file for the assemblies that are now part of the .NET Framework.
|
||
|
|
- Re-target your application to target the .NET Framwork 4.7.1
|
||
|
|
|