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:

Could not load file or assembly Microsoft.Extensions.DependencyInjection.Abstractions, Version=1.1.0.0

When using .Net Standard 1.4 in a library and .Net framework 4.6.1 in and application, unable to load file System.IO.FileSystem, Version=4.0.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.

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

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;
    }

}

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.

This is actually much easier than hacking config files. Hacking config files is a little scary; you might miss something! Let the IDE do it for you - hopefully it will do it right!

1. Right click solution
2. Click Manage Nuget Packages for Solution...
3. Search for System.ComponentModel.Annotations
4. Put a check box in your test projects and click Install

Now my unit tests run! Awesome!

It is still possible that you will need to use @Guillaume's answer if you have app.config files in your unit test project.

Please Add below dependentAssembly in your web.Config or app.Config file

The following configuration is added under the configuration --> runtime --> assemblyBinding node under:

<dependentAssembly>
        <assemblyIdentity name="System.ComponentModel.Annotations" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.2.1.0" newVersion="4.2.1.0" />
      </dependentAssembly>

Credit to @MiguelSlv as my case had to do with using a proper binding redirect. However, be sure that when you deploy your app to beta or production that the binding redirect is in your deployed web.config (not just in your development environment). I ended up using the following binding redirect for the NuGet package System.ComponentModel.Annotations 5.0.0 that is used in a .NET Standard 2.0 class project being consumed by my **ASP.NET MVC web application (.NET Framework 4.7.1)

<dependentAssembly>
<assemblyIdentity name="System.ComponentModel.Annotations" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-4.2.1.0" newVersion="4.2.1.0" />
</dependentAssembly>

Note that 4.2.1.0 is the version shown under properties, while 5.0.0 is the NuGet package version.

Fixed this by installing the same System.ComponentModel.Annotations version I want to use across all the projects in the solution.

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

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 fixed this error by doing the Clean Solution command in Visual Studio 2019.

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:

1. From package manage console do:

   Get-Project –All | Add-BindingRedirect

   to regenerate assemblyBinding configuration at the config file

2. 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:

   1. X is the version that can't be load, from the error message
   2. Y is the version on your project references. To get it, select the library from the references node, and look for the version on property pane.

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
}