Skip to main content

Return to Answer

remove mistake
Source Link
yu yang Jian
yu yang Jian
  • 7.3k
  • 8
  • 61
  • 88

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

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

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<add assembly> tag from my web.config resolved the issue.

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

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

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.

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

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

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.

remove mistake
Source Link
edit approved Nov 27, 2020 at 9:16
SwissCodeMen
edit approved Nov 27, 2020 at 9:16
SwissCodeMen
  • 5k
  • 10
  • 31
  • 39

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

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

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"add assembly tag from my web.configweb.config resolved the issue.

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

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

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.

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

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

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.

Source Link
Silas Humberto Souza
Silas Humberto Souza
  • 176
  • 1
  • 3

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

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

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.