Visual Studio 2017 - Could not load file or assembly System Runtime Version 4 1 0 0 or one of its dependencies

Question

I am using Visual Studio 2017 and am trying to create a  Net Standard 1 5 library and use it in a  Net 4 6 2 nUnit test project    I am getting the following error        Could not load file or assembly  System Runtime  Version 4 1 0 0    Culture neutral  PublicKeyToken b03f5f7f11d50a3a  or one of its   dependencies  The system cannot find the file specified    I have tried the following    Reference Std library as project reference  Error  gives me the previous error  Create a NuGet pkg for my Std library and reference that  Error  The type is System String  expecting System String  This is because System Runtime ended up getting referenced by the project and it has definitions for all the standard types  Reference NuGet pkg NetStandard Library  Error  give me the same error as     The type is System String  expecting System String    NOTE  Before I did this  I cleared ALL NuGet packages from the project and then added just the nUnit and NetStandard Library packages  which installed 45 other packages     Is this a bug  Is there a work-around  Any help is appreciated

User · Answer

I had this error occur when building an Azure Function (with a queue trigger, should it make a difference)

The issue in this case was because the AzureFunctionsVersion was set to v2 instead of v3. To update it via VS2019, unload the project then edit the csproj file. Within the PropertyGroup node, add/edit the following:

<PropertyGroup>
  <AzureFunctionsVersion>v3</AzureFunctionsVersion>
</PropertyGroup>

User · Answer

I m using ASP Net CORE 2 1 and I got this error when I ran by selecting a  csproj from a list of about 40 in a big repo  When I opened the csproj file individually  the error was resolved  Something with how the program was launched was different when the csproj was opened

User · Answer

I have also gone through this error and sharing how i got rid off to it   In my case below line existed in web config of webapi project but there was not package reference in package config file   Code in Web config in Webapi Project   lt dependentAssembly gt       lt assemblyIdentity name  System Runtime  publicKeyToken  B03F5F7F11D50A3A  culture  neutral    gt       lt bindingRedirect oldVersion  0 0 0 0-4 1 2 0  newVersion  4 3 0    gt   lt  dependentAssembly gt    Code I Added in packages config file in web api project Before closing of  element    lt package id  System Runtime  version  4 3 0  targetFramework  net461    gt    Another Solution Worked in My Case   Another Sure short that may work in case you copied project to another Computer system that may have little different package versions that you can try changing assembly version to version given in error on website   webapi when you run it  Like in this case as given in question Version needed is  4 1 0 0  so simply try changing current version in web config to version shown in error as below  Error   Could not load file or assembly  System Runtime  Version 4 1 0 0  or one of its dependencies

User · Answer

I had a project with the same problem   I solved it with change dotnet core version from 2 2 to 2 0  If your problem has remained   Try this solution

User · Answer

it is too late I know  howewer there is no succesfully answer  I found the answer from another website  I fixed the issue when I delete the System Runtime assemblydependency  I deleted this    lt dependentAssembly gt   lt assemblyIdentity name  System Runtime  publicKeyToken  b03f5f7f11d50a3a  culture  neutral   gt   lt bindingRedirect oldVersion  0 0 0 0-4 1 2 0  newVersion  4 1 2 0   gt   lt  dependentAssembly gt    Best Regards

User · Answer

I had a similar problem in VS 2017 15 45 - I found when I checked that even though the project compiled and ran it came up with a system IO FileNotFoundException with regard to System Runtime when I tried to access TPL Dataflow objects   When I checked the projects in the solution  one of them  the top one  was missing the System Runtime package used by the underlying projects  Once I installed it from Nuget it all worked correctly

User · Answer

I had the same problem and no suggested solutions that I found worked  My solution for this issue was  Check App config and packages config to see if the versions match   Originally my app config contained    lt dependentAssembly gt     lt assemblyIdentity name  System Runtime  publicKeyToken  b03f5f7f11d50a3a  culture  neutral    gt     lt bindingRedirect oldVersion  0 0 0 0-4 1 1 0  newVersion  4 1 1 0    gt   lt  dependentAssembly gt    But the packages config contained    lt package id  System Runtime  version  4 3 0  targetFramework  net461  requireReinstallation  true    gt    I modified the app config entry to match packages config for the newVersion    lt dependentAssembly gt     lt assemblyIdentity name  System Runtime  publicKeyToken  b03f5f7f11d50a3a  culture  neutral    gt     lt bindingRedirect oldVersion  0 0 0 0-4 1 1 0  newVersion  4 3 0    gt   lt  dependentAssembly gt    After the change  the issue was resolved

User · Answer

This issue happens when you reference a  NET Standard project from a  NET 4 x project  none of the  NET Standard project s nuget package references are brought in as dependencies   I resolved by add System Runtime 4 3 and NETStandard Library package and   important   I use refactor tool to look up the System Runtime dll version  It is 4 1 1 1 not 4 3 and then add an  bindingRedirect in  config   lt dependentAssembly gt       lt assemblyIdentity name  System Runtime  publicKeyToken  b03f5f7f11d50a3a  culture  neutral    gt       lt bindingRedirect oldVersion  0 0 0 0-5 0 0 0  newVersion  4 1 1 1    gt   lt  dependentAssembly gt

User · Answer

I ended up in this situation several times with my  NET 4 6 1 web site  I created the problem each time when I added a reference to a separate  NET Core project  Upon building  Visual Studio correctly alerted me that such cross-framework references are invalid  and I quickly deleted the project reference  The project built fine after that  but the System Runtime error appeared when accessing the web site and refused to go away   The fix each time was lame but effective  I deleted the project directory and redownloaded it from source control  Even though there was no difference between before and after  I was able to build the project and access the page with no complaints

User · Answer

I resolved that error by referencing the NetStandard Library and the following app config File in the NUnit-Project    lt  xml version  1 0  encoding  utf-8   gt   lt configuration gt   lt runtime gt       lt assemblyBinding xmlns  urn schemas-microsoft-com asm v1  gt           lt dependentAssembly gt               lt assemblyIdentity name  System Runtime  publicKeyToken  b03f5f7f11d50a3a  culture  neutral    gt               lt bindingRedirect oldVersion  0 0 0 0-4 1 1 0  newVersion  4 1 1 0    gt           lt  dependentAssembly gt           lt dependentAssembly gt               lt assemblyIdentity name  System Reflection  publicKeyToken  b03f5f7f11d50a3a  culture  neutral    gt               lt bindingRedirect oldVersion  0 0 0 0-4 1 1 0  newVersion  4 1 1 0    gt           lt  dependentAssembly gt           lt dependentAssembly gt               lt assemblyIdentity name  System Runtime InteropServices  publicKeyToken  b03f5f7f11d50a3a  culture  neutral    gt               lt bindingRedirect oldVersion  0 0 0 0-4 1 0 0  newVersion  4 1 1 0    gt           lt  dependentAssembly gt       lt  assemblyBinding gt   lt  runtime gt      Edit  If anything other than System Runtime  System Reflection or System Runtime InteropServices is missing  e g  System Linq   then just add a new dependentAssembly node   Edit 2  In new Visual Studio Versions  2017 15 8 I think  it s possible that Studio creates the app config File  Just check the Auto-generate binding redirects Checkbox in Project-Properties - Application    Edit 3    Auto-generate binding redirects does not work well with  NET Classlibraries  Adding the following lines to the csproj files solves this and a working  config file for the Classlibary will be generated    lt PropertyGroup gt     lt AutoGenerateBindingRedirects gt true lt  AutoGenerateBindingRedirects gt     lt GenerateBindingRedirectsOutputType gt true lt  GenerateBindingRedirectsOutputType gt   lt  PropertyGroup gt

User · Answer

If it s working previously  then there should be an App config change  Undo App config worked for me

User · Answer

For me  it was the missing  web config  file  After adding it to the deployed project directory in asp net core 3 1 app  the problem was solved

User · Answer

I encounter this issue recently and I tried many things mentioned in this thread and others  I added package reference for  System Runtime  by nuget package manager  fixed the binding redicts in app config  and make sure that app config and package config have the same version for the assembly  However  the problem persisted    Finally  I removed the  lt dependentAssembly gt  tag for the assembly and the problem dissappeared  So  try removing the following in your app config    lt dependentAssembly gt       lt assemblyIdentity name  System Runtime  publicKeyToken  b03f5f7f11d50a3a  culture  neutral    gt       lt bindingRedirect oldVersion  0 0 0 0-4 1 0 0  newVersion  4 1 1 0    gt   lt  dependentAssembly gt    Edit  After I update  NET framework to 4 7 2  the problem resurfaced  I tried the above trick but it didn t work  After wasting many hours  I realized the problem is occurring because of an old System Linq reference in app config  Therefore  either remove or update all Linq references also to get rid of this problem

User · Answer

Ran into this just now in a Unit Test project after adding MsTest V2 through Nuget   Renaming app config  so effectively removing it  did the trick for me   Having read through all the above posts  I m still not sure why  sorry

User · Answer

We have found that AutoGenerateBindingRedirects might be causing this issue   Observed  the same project targeting net45 and netstandard1 5 was successfully built on one machine and failed to build on the other  Machines had different versions of the framework installed  4 6 1 - success and 4 7 1 - failure   After upgrading framework on the first machine to 4 7 1 the build also failed   Error Message   System IO FileNotFoundException   Could not load file or assembly  System Runtime  Version 4 1 0 0  Culture neutral  PublicKeyToken b03f5f7f11d50a3a  or one of its dependencies  The system cannot find the file specified    ---- gt  System IO FileNotFoundException   Could not load file or assembly  System Runtime  Version 4 0 0 0  Culture neutral  PublicKeyToken b03f5f7f11d50a3a  or one of its dependencies  The system cannot find the file specified    Auto binding redirects is a feature of  net 4 5 1  Whenever nuget detects that the project is transitively referencing different versions of the same assembly it will automatically generate the config file in the output directory redirecting all the versions to the highest required version   In our case it was rebinding all versions of System Runtime to Version 4 1 0 0   net 4 7 1 ships with a 4 3 0 0 version of runtime  So redirect binding was mapping to a version that was not available in a contemporary version of framework   The problem was fixed with disabling auto binding redirects for 4 5 target and leaving it for  net core only    lt PropertyGroup Condition     TargetFramework       net45   gt     lt AutoGenerateBindingRedirects gt false lt  AutoGenerateBindingRedirects gt   lt  PropertyGroup gt

User · Answer

Into app config or web config add   lt dependentAssembly gt       lt assemblyIdentity name  System Runtime  publicKeyToken  b03f5f7f11d50a3a  culture  neutral   gt       lt bindingRedirect oldVersion  0 0 0 0-5 0 0 0  newVersion  4 0 0 0   gt   lt  dependentAssembly gt

User · Answer

I had an issue with this in an NUnit 2 6 4 project targeting dotnet framework 4 6 2  I ran into that System Runtime FileNotFound error trying to use Humanizer   I fixed my error by installing NetStandard Library into my unit test project

User · Answer

Trust me  I am not joking  Remove all the System Runtime dependencies from your app config and it will start working

User · Answer

I solve this issue by switching from  NET 4 7 2     NET 4 5 2 and then switch back to 472  So in some cases this error  occurs because package manager unable resolve dependences

User · Answer

I fixed the problem by removing the Nuget Package System Runtime and then reinstalling it

User · Answer

This issue has many causes    in my case the problem was that in my web config a tag adding the System Runtime assembly   lt assemblies gt       lt add assembly  quot System Runtime  Version 4 0 0 0  Culture neutral  PublicKeyToken b03f5f7f11d50a3a quot    gt   lt  assemblies gt   but one package also added the same assembly as dependency with other version   lt package id  quot System Runtime quot  version  quot 4 3 0 quot  targetFramework  quot net47 quot    gt   removing the  lt add assembly gt  tag from my web config resolved the issue

User · Answer

I fixed it by deleting my app config with    lt assemblyIdentity name  System Runtime       gt     entries   app config was automatically added  but not needed  during refactoring

User · Answer

I tried all the solutions here  but to no avail  Eventually  I solved it by opening the new csproj file and manually added the following section    lt Reference Include  System Runtime  Version 4 1 1 0  Culture neutral  PublicKeyToken b03f5f7f11d50a3a  gt   lt HintPath gt    packages System Runtime 4 3 0 lib net462 System Runtime dll lt  HintPath gt   lt  Reference gt

User · Answer

Seems like the issue is caused when there is version conflict between packages config and app config  In app config you have assembly binding redirects automatically generated by thing called  AutoGenerateBindingRedirects   When enabled each time you download nuget package it will  additionaly to making new entry in packages config  add this binding redirect information to app config  what s the purpose of this is explained here  Assembly Binding redirect  How and Why   There you can read what user  Evk wrote      Why are binding redirects needed at all  Suppose you have application   A that references library B  and also library C of version 1 1 2 5    Library B in turn also references library C  but of version 1 1 1 0    Now we have a conflict  because you cannot load different versions of   the same assembly at runtime  To resolve this conflict you might use   binding redirect  usually to the new version   So  QUICK FIX  Remove all  entries in app config   In my case just by doing that program started working  but it will probably work only if you don t have any version conflicts of the same assembly at runtime   If you do have such conflict you should fix these version numbers in app config to match actually used versions of assemblies  but manual process is painful  so I suggest to auto-generate them again by opening Package Manager Console and perform packages reinstallation by typing Update-Package -reinstall

User · Answer

Before running the unit tests  just remove the runtime tags from app config file  Problem  will be solved

User · Answer

This issue happens when you reference a  NET Standard project from a  NET 4 x project  none of the  NET Standard project s nuget package references are brought in as dependencies   To fix this  you need to ensure your  NET 4 x csproj file is pointing to current build tools  at least 14     lt Project ToolsVersion  15 0  gt       The below should no longer be needed  it was fixed around VS 15 3   There was a known bug in VS2017  specifically in NuGet 4 0   To work around the bug  you ll need to open up the  csproj file for your  NET 4 x project and add this snippet    lt ItemGroup gt     lt PackageReference Include  Legacy2CPSWorkaround  Version  1 0 0  gt       lt PrivateAssets gt All lt  PrivateAssets gt     lt  PackageReference gt   lt  ItemGroup gt    NuGet 4 x brings with it the  package reference  -- no more packages config -- but the old 4 x pipeline was not fully updated at the time of VS2017 s launch  The above snippet seems to  wake up  the build system to correctly include package references from dependencies

[.net] Visual Studio 2017 - Could not load file or assembly 'System.Runtime, Version=4.1.0.0' or one of its dependencies

Examples related to .net

Examples related to visual-studio-2017

Examples related to .net-standard-1.5