assembly-binding-redirect

Assembly binding added in compiled output (app.config)

我怕爱的太早我们不能终老 提交于 2021-01-28 07:31:38
问题 If I compile my application, an assembly binding is added automatically in the output. The specific assembly binding is not in the app.config in Visual Studio but in the created application config. Is there any way, to check why the assembly binding is added automatically? The option AutoGenerateBindingRedirects is not enabled. I don't want to have the following assembly binding <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="System.IO

Projects with same nuget package referencing different version of assembly

不打扰是莪最后的温柔 提交于 2020-07-16 06:18:30
问题 I am going mad here, and I am hoping that it's something that I've simply overlooked. I am experiencing intermittent FileLoadExceptions , which are showing up after deployments even if the code change between deployments doesn't change any assembly references . Looking at the most recent example of this, I am seeing a FileLoadException due to System.IO.Compression , version 4.2.0.0 not being found. In all cases, we are referencing the System.IO.Compression nuget package, version 4.3.0 .

Two different versions of Newtonsoft.Json.dll needed in ASP.NET MVC

好久不见. 提交于 2020-02-23 12:43:37
问题 I have developed a MVC application that has dependency on Connectwise SDK that uses Newtonsoft.Json.dll v6.0.0.0 and Dropbox SDK that uses Newtonsoft.Json.dll v7.0.0.0. I need to ensure that my project uses the appropriate dll when needed. After researching, I tried the following: - Placed the 2 dlls under sub-folders /dlls/6.0.0.0/ and /dlls/7.0.0.0 resp. - Referenced version 6.0.0.0 dll in project References - Added to web.config <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

Two different versions of Newtonsoft.Json.dll needed in ASP.NET MVC

▼魔方 西西 提交于 2020-02-23 12:42:52
问题 I have developed a MVC application that has dependency on Connectwise SDK that uses Newtonsoft.Json.dll v6.0.0.0 and Dropbox SDK that uses Newtonsoft.Json.dll v7.0.0.0. I need to ensure that my project uses the appropriate dll when needed. After researching, I tried the following: - Placed the 2 dlls under sub-folders /dlls/6.0.0.0/ and /dlls/7.0.0.0 resp. - Referenced version 6.0.0.0 dll in project References - Added to web.config <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

How to achieve assembly binding redirect in a plugin scenario?

♀尐吖头ヾ 提交于 2020-01-24 07:49:11
问题 I have a plugin P extending and application A (.NET40) that I have no control over. The P assembly (.NET40) has a shared dependency D (.NET35). Both P and D depend on FSharp.Core, but different versions: P is compiled against FSharp.Core, Version=4.4.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a D is compiled against FSharp.Core, Version=2.3.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a Only FSharp.Core, Version=4.4.0.0 is deployed and I subscribe to AppDomain.AssemblyResolve