I have a .NET Standard 1.4 class library that references the System.ComponentModel.Annotations (4.3.0) NuGet package.
I'm then referencing this class library from a .NET Framework 4.6.2 test project. It builds fine, but at runtime I get the following error:
System.IO.FileLoadException occurred HResult=0x80131040
Message=Could not load file or assembly 'System.ComponentModel.Annotations, Version=4.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
I tried adding a reference to the System.ComponentModel.Annotations (4.3.0) NuGet package from the net462 project, but that didn't make any difference.
I tried adding a reference to the .NET Standard library from the net462 project, but still no luck.
Am I missing something here? Is this a known bug, if so is there a work around?
Any help is much appreciated!
In many cases, this can be solved by adding the following code to the csproj file of your test project:
<PropertyGroup>
<AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>
<GenerateBindingRedirectsOutputType>true</GenerateBindingRedirectsOutputType>
</PropertyGroup>
This forces the build process to create a .dll.config
file in the output directory with the needed binding redirects.
The reason is that "classic" csproj test projects are true "libraries" and are not considered to need binding redirects by default. But running unit tests requires this. This only becomes an issue if referenced projects need those redirects to work correctly. This usually works when directly installing all NuGet packages that the referenced library uses, but with the new PackageReference
style of NuGet packages, it does not.
See other instances where this fix has helped:
I had similar problem but none of the above answers helped me. It turns out that solution is very easy, I've just run following command in Package Manager:
Install-Package System.ComponentModel.Annotations -Version 4.1.0
In my case, I was using 4.0.0, so I fixed it by adding in
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.ComponentModel.Annotations"
publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
<bindingRedirect oldVersion="4.1.0.0" newVersion="4.0.0.0"/>
</dependentAssembly>
Adapt to your required version.
This usually happens when visual studio can't figure out the correct bindingRedirect.
Most likely the cause it that the version of the nugget does not match the version of the produced library.
To fix do this:
From package manage console do:
Get-Project –All | Add-BindingRedirect
to regenerate assemblyBinding
configuration at the config file
If didn't fix it, then add manually the binding redirection:
<dependentAssembly>
<assemblyIdentity name="System.ComponentModel.Annotations" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-X" newVersion="Y" />
</dependentAssembly>
where:
Got it working by using assembly redirection as described in:
just invoke FunctionsAssemblyResolver.RedirectAssembly()
in the begining of your program.
https://stackoverflow.com/a/50776946/2705777
using System.Reflection;
using System.Diagnostics;
using System.Linq;
public class FunctionsAssemblyResolver
{
public static void RedirectAssembly()
{
var list = AppDomain.CurrentDomain.GetAssemblies().OrderByDescending(a => a.FullName).Select(a => a.FullName).ToList();
AppDomain.CurrentDomain.AssemblyResolve += CurrentDomain_AssemblyResolve;
}
private static Assembly CurrentDomain_AssemblyResolve(object sender, ResolveEventArgs args)
{
var requestedAssembly = new AssemblyName(args.Name);
Assembly assembly = null;
AppDomain.CurrentDomain.AssemblyResolve -= CurrentDomain_AssemblyResolve;
try
{
assembly = Assembly.Load(requestedAssembly.Name);
}
catch (Exception ex)
{
}
AppDomain.CurrentDomain.AssemblyResolve += CurrentDomain_AssemblyResolve;
return assembly;
}
}
I fixed this error by doing the Clean Solution command in Visual Studio 2019.
Fixed this by installing the same System.ComponentModel.Annotations version I want to use across all the projects in the solution.
For me, none of the other solutions worked.
I resolved this by manually adding a reference to System.ComponentModel.DataAnnotations
myself (via project -> References), rather than letting Visual Studio handle it via the light-bulb quick-fix menu.
Also for 4.2.0.0
version error this is fixed for me in web.config
:
<dependentAssembly>
<assemblyIdentity name="System.ComponentModel.Annotations" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-4.2.1.0" newVersion="4.6.0" />
</dependentAssembly>
</assemblyBinding>
I have this issue by implementing a helper function redirecting the assembly at the begin (which was suggested in this answer):
public static class FunctionsAssemblyResolver
{
#region Public Methods
public static void RedirectAssembly()
{
AppDomain.CurrentDomain.AssemblyResolve += ResolveAssemblyOnCurrentDomain;
}
#endregion Public Methods
#region Private Methods
private static Assembly ResolveAssemblyOnCurrentDomain(object sender, ResolveEventArgs args)
{
var requestedAssembly = new AssemblyName(args.Name);
var assembly = default(Assembly);
AppDomain.CurrentDomain.AssemblyResolve -= ResolveAssemblyOnCurrentDomain;
try
{
assembly = Assembly.Load(requestedAssembly.Name);
}
catch
{ }
AppDomain.CurrentDomain.AssemblyResolve += ResolveAssemblyOnCurrentDomain;
return assembly;
}
#endregion Private Methods
}
Linux Users
You may have to install mono if you're trying to generate .exe file from linux system.
See this link on how to install mono on ubuntu 20.04
User contributions licensed under CC BY-SA 3.0