Visual Studio 2017-파일 또는 어셈블리 'System.Runtime, Version ='또는 해당 종속성 중 하나를로드 할 수 없습니다.

lottogame 2020. 9. 15. 19:12

Visual Studio 2017-파일 또는 어셈블리 'System.Runtime, Version ='또는 해당 종속성 중 하나를로드 할 수 없습니다.

Visual Studio 2017을 사용하고 있으며 .Net Standard 1.5 라이브러리를 만들고 .Net 4.6.2 nUnit 테스트 프로젝트에서 사용하려고합니다.

다음과 같은 오류가 발생합니다.

파일 또는 어셈블리 'System.Runtime, Version =, Culture = neutral, PublicKeyToken = b03f5f7f11d50a3a'또는 해당 종속성 중 하나를로드 할 수 없습니다. 시스템이 지정된 파일을 찾을 수 없습니다.

나는 다음을 시도했다 :

  1. 프로젝트 참조로 Std 라이브러리를 참조하십시오. 오류 : 이전 오류를 표시합니다.
  2. 내 Std 라이브러리에 대한 NuGet pkg를 만들고 참조하십시오. 오류 : 형식은 System.String이며 System.String이 필요합니다. 이는 System.Runtime이 결국 프로젝트에서 참조되고 모든 표준 형식에 대한 정의가 있기 때문입니다.
  3. 참조 NuGet pkg NetStandard.Library. 오류 : # ( "형식은 System.String, System.String 예상")과 동일한 오류를 제공합니다. 참고 :이 작업을 수행하기 전에 프로젝트에서 모든 NuGet 패키지를 지운 다음 nUnit 및 NetStandard.Library 패키지 (45 개의 다른 패키지를 설치 함) 만 추가했습니다.

이것은 버그입니까? 해결 방법이 있습니까? 도움을 주시면 감사하겠습니다.

나는 똑같은 문제가 있었고 내가 찾은 제안 된 해결책이 없었다. 이 문제에 대한 내 해결책은 App.config 및 packages.config를 확인하여 버전이 일치하는지 확인하는 것입니다.

원래 내 app.config에는 다음이 포함되었습니다.

  <assemblyIdentity name="System.Runtime" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
  <bindingRedirect oldVersion="" newVersion="" />

그러나 packages.config에는 다음이 포함되었습니다.

<package id="System.Runtime" version="4.3.0" targetFramework="net461" requireReinstallation="true" />

newVersion에 대한 packages.config와 일치하도록 app.config 항목을 수정했습니다.

  <assemblyIdentity name="System.Runtime" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
  <bindingRedirect oldVersion="" newVersion="4.3.0" />

변경 후 문제가 해결되었습니다.

이 문제는 .NET 4.x 프로젝트에서 .NET Standard 프로젝트를 참조 할 때 발생합니다. .NET Standard 프로젝트의 nuget 패키지 참조는 종속성으로 가져 오지 않습니다.

이 문제를 해결하려면 .NET 4.x csproj 파일이 현재 빌드 도구 (최소 14 개)를 가리키는 지 확인해야합니다.

<Project ToolsVersion="15.0">...

아래는 더 이상 필요하지 않으며 VS 15.3에서 수정되었습니다.

있었다 알려진 버그 VS2017에서 특히 NuGet 4.0.

버그를 해결하려면 .NET 4.x 프로젝트 용 .csproj 파일을 열고 다음 코드 조각을 추가해야합니다.

  <PackageReference Include="Legacy2CPSWorkaround" Version="1.0.0">

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.

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 <dependentAssembly> tag for the assembly and the problem dissappeared. So, try removing the following in your app.config.

    <assemblyIdentity name="System.Runtime" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
    <bindingRedirect oldVersion="" newVersion="" />

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.

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

I fixed it by deleting my app.config with

<assemblyIdentity name="System.Runtime" ....> 


app.config was automatically added (but not needed) during refactoring

I resolved that error by referencing the NetStandard.Library and the following app.config File in the NUnit-Project.

<?xml version="1.0" encoding="utf-8"?>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
            <assemblyIdentity name="System.Runtime" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
            <bindingRedirect oldVersion="" newVersion="" />
            <assemblyIdentity name="System.Reflection" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
            <bindingRedirect oldVersion="" newVersion="" />
            <assemblyIdentity name="System.Runtime.InteropServices" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
            <bindingRedirect oldVersion="" newVersion="" />


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. Auto-generate binding redirects

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.


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=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
  ----> System.IO.FileNotFoundException : Could not load file or assembly 'System.Runtime, Version=, 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= .net 4.7.1 ships with a 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.

<PropertyGroup Condition="'$(TargetFramework)' == 'net45'">

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 not 4.3 and then add an bindingRedirect in .config

    <assemblyIdentity name="System.Runtime" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
    <bindingRedirect oldVersion="" newVersion="" />

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.

<dependentAssembly> <assemblyIdentity name="System.Runtime" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/> <bindingRedirect oldVersion="" newVersion=""/> </dependentAssembly>

Best Regards

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.

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.

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!

This issue has many causes... in my case the problem was that was in my web.config a tag adding the System.Runtime assembly:

    <add assembly="System.Runtime, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />

but one package also added the same assembly as dependency with other version:

<package id="System.Runtime" version="4.3.0" targetFramework="net47" />

removing the "add assembly" tag from my web.config resolved the issue.

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

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

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.

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:

<Reference Include="System.Runtime, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a">

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.

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

Into app.config or web.config add

    <assemblyIdentity name="System.Runtime" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
    <bindingRedirect oldVersion="" newVersion=""/>

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

참고URL :