Question posted in
The official documentation can be found here.

Redis – Could not load file or assembly System.Runtime.CompilerServices.Unsafe

I created a Visual Studio (Community 2019) project with C# using ServiceStack.Redis. Since it is C#, I use Windows 10 (there is a Redis version for Windows but it is really old and as I know, it is unofficial so I am afraid that might be the problem).
Here is an excerpt from my code:

public class PeopleStorage: IDisposable
{
    public PeopleStorage()
    {
        redisManager = new RedisManagerPool("localhost");
        redis = (RedisClient)redisManager.GetClient();
        facts = (RedisTypedClient<List<Fact>>)redis.As<List<Fact>>();
    }

    public List<Fact> GetFacts(int id)
    {
        string sid = id.ToString();
        if (facts.ContainsKey(sid))
            return facts[sid];
        return accessor.GetFacts(id);
    }

    private RedisTypedClient<List<Fact>> facts;
    private RedisClient redis;
    private RedisManagerPool redisManager;
}

In an attempt to connect to Redis in line return facts[sid];, an exception occurs:

System.IO.FileLoadException: "Could not load file or assembly
"System.Runtime.CompilerServices.Unsafe, Version=4.0.4.1,
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" or one of it’s
dependences. The found Assembly’s manifest definition does not match
the Assembly reference. (Exception from HRESULT: 0x80131040)"

(May be inaccurate as I have translated it)

I have tried updating all the packages, starting with ServiceStack packages, ending with System.Runtime.CompilerServices.Unsafe itself. Moreover, you can’t choose 4.0.4.1 version in NuGet, the closest one there is 4.0.0, while the relevant is 4.0.7.

I do not understand why it uses this version and how I can fix this problem.
Even a clean reinstall of Visual Studio did not help.

Tags:

12

Answers


  1. 0

    I assume that you’re using the .NET Framework. This error is known for ServiceStack.Redis and is tracked on GitHub. It occurs because you use libraries that depend on different versions of System.Runtime.CompilerServices.Unsafe. These transitive dependencies need to be resolved and consolidated to end up with one assembly in your output folder. You will end up with the latest of these versions. Consequently, if one of the libraries depends on a specific version that is older, it will not be found.

    The bug that causes this issue is fixed in System.Runtime.CompilerServices.Unsafe 4.6.0. Use binding redirects, to load the specific version of the assembly that you need. Insert this snippet into all of your app.config files.

    <dependentAssembly>
    <assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-4.0.6.0" newVersion="4.0.6.0" />
</dependentAssembly>

    You need to specify the assembly version of the assembly that you need as newVersion. This is not the same as the package version that you choose when installing your NuGet package. They correspond like this:

    • Package 4.5.3 contains assembly version is 4.0.4.1
    • Package 4.7.0 contains assembly version 4.0.6.0

    In this binding redirect I use the newer version of System.Runtime.CompilerServices.Unsafe that fixes the bug. However, if you depend on the older version, use 4.0.4.1.

    Login or Signup to reply.
  2. 0

    Could not load file or assembly System.Runtime.CompilerServices.Unsafe

    It seems that you have installed System.Runtime.CompilerServices.Unsafe nuget package 4.5.3 version. And it corresponds to System.Runtime.CompilerServices.Unsafe.dll assembly version 4.0.4.1.

    Suggestion

    1) Please try to register System.Runtime.CompilerServices.Unsafe version 4.0.4.1 into GAC so that the system can it.

    • Run Developer Command Prompt for VS2019 as Administrator

    • type:

      cd xxxxx (the path of the the System.Runtime.CompilerServices.Unsafe 4.0.4.1)

gacutil /i System.Runtime.CompilerServices.Unsafe.dll

    2) If you use Net Framework projects with xxx.config file, you could use bindingRedirect.

    Add these in app.config file or web.config file:

    <configuration>  
   <runtime>  
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">  
         <dependentAssembly>  
            <assemblyIdentity name="System.Runtime.CompilerServices.Unsafe"  
                              publicKeyToken="b03f5f7f11d50a3a"  
                              culture="neutral" />  
            <bindingRedirect oldVersion="0.0.0.0-4.0.4.1"  
                             newVersion="4.0.4.1"/>  
         </dependentAssembly>  
      </assemblyBinding>  
   </runtime>  
</configuration>

    Besides, if you update System.Runtime.CompilerServices.Unsafe nuget package version to the newer version, you should also changed the bindingRedirect assembly version.

    You can refer to these assembly versions of System.Runtime.CompilerServices.Unsafe

    4.5.x is System.Runtime.CompilerServices.Unsafe nuget package version while 4.0.x.x is System.Runtime.CompilerServices.Unsafe.dll assembly version.

    4.5.0 is 4.0.4.0 
4.5.1 is 4.0.4.0 
4.5.2 is 4.0.4.0 
4.5.3 is 4.0.4.1
4.6.0 is 4.0.5.0
4.7.0 is 4.0.6.0
4.7.1 is 4.0.6.1
5.0.0 is 5.0.0.0
    Login or Signup to reply.
  3. 0

    In my experience, I didn’t need to install System.Runtime.CompilerServices.Unsafe because it is referenced from another package, npgsql.
    Instead, what I did is as follow:

    1. Insert this code snippet to app.config of the project
     <configuration>
    <runtime>
        <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
          <dependentAssembly>
            <assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-4.0.6.0" newVersion="4.0.6.0" />
          </dependentAssembly>
          <dependentAssembly>
            <assemblyIdentity name="System.Numerics.Vectors" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-99.9.9.9" newVersion="4.1.4.0" />
          </dependentAssembly>
          <dependentAssembly>
            <assemblyIdentity name="System.Threading.Tasks.Extensions" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral"/>
            <bindingRedirect oldVersion="0.0.0.0-4.2.0.1" newVersion="4.2.0.1"/>
          </dependentAssembly>
        </assemblyBinding>
      </runtime>
    </configuration>
    1. Run again the project

    This is the solution I found so far, to add dependentAssembly bindingReference

    Login or Signup to reply.
  4. 0

    Based on Perry’s answer, I simply installed the nuget package System.Runtime.CompilerServices.Unsafe version 4.5.3 and the problem was solved.

    Login or Signup to reply.
  5. 0

    Recently I encountered exactly the same error message. However, that message did not appear in all PCs that I used to test my app. Some PCs yielded the error message but some others are not. I couldn’t differentiate which are the characteristics of PC that would be generating error message and which ones did not. It seemed.. random.

    Then I noticed a warning message when I compiled my app (I was using Visual Studio 2019 at the time):

    Severity Code Description Project File Line Suppression State
    Warning Found conflicts between different versions of the same dependent assembly. Please set the "AutoGenerateBindingRedirects" property to true in the project file. For more information, see http://go.microsoft.com/fwlink/?LinkId=294190. SQL Online Exam System

    And I did exactly what it told me:

    enter image description here

    Then the problem was solved.

    Login or Signup to reply.
  6. 0

    My problem was solved by deleting the "bin" and "obj" folders.

    Login or Signup to reply.
  7. 0

    Thanks @thatguy finally was able to resolve the issue.

    The solution that worked for me was from Nick Craver with details as below:

    Things to try:

    ** Reference the System.Runtime.CompilerServices.Unsafe library directly
    as a (so VS alerts it needs a binding and offers a
    one-click fix…sometimes it won’t realize this transitively).

    ** If using app.config, remove all binding redirects and add a
    true
    property up on the top.

    This is a load errors and I really really really wish
    they had a wiki page explaining how to fix this because it can plague
    any library anyway if you step on one of the magical landmines.

    Login or Signup to reply.
  8. 0

    In my case, a Visual Studio update helps.

    Login or Signup to reply.
  9. 0

    My app is a native EXE which loads .NET assemblies; we have no app.config file. Assembly config files are not loaded and used at runtime. So the approach I took to solve this was based on helpful answers here and here.

    The idea is to catch the assembly load exception and handle it by substituting whatever existing (higher versioned) System.Runtime.CompilerServices.Unsafe assembly is already loaded.

    Add this somewhere early in application startup:

    AppDomain.CurrentDomain.AssemblyResolve += 
    new ResolveEventHandler(CurrentDomain_AssemblyResolve);

    And this is the event handler:

    Assembly CurrentDomain_AssemblyResolve(object sender, ResolveEventArgs args)
{
    var name = new AssemblyName(args.Name);
    if (name.Name == "System.Runtime.CompilerServices.Unsafe")
    {
        return typeof(System.Runtime.CompilerServices.Unsafe).Assembly;
    }
    return null;
}

    This worked great in my situation. I also happen to think this is a little more discoverable than potentially cryptic settings in app.config (IMO) so it might be a good solution in general.

    Login or Signup to reply.
  10. 0

    In my case, everything was working but I started getting this message after a merge.

    None of the solutions worked because everything was setup correctly. My dll version was 6.0, so I downgraded to 5.0, ran the project (successfully) and then upgraded to 6.0 and then ran it again. Worked perfectly.

    Hope this helps someone.

    Login or Signup to reply.
  11. 0

    In my case I installed the latest 6.0.0.0 package across my solution (including the net 472 web apps!) and then added a binding redirect to version 6

    
      <dependentAssembly>
        <assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0"/>
      </dependentAssembly>
    Login or Signup to reply.
  12. 0

    In my case, the package/assembly reference entry was not present in the web.config file at all.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search