assembly-binding-redirect

I have an internal NuGet package that contains a single dll, no external NuGet package dependencies, and no web.config transforms. Yet when i run Update-Package on my projects (class lib and website) for this specific NuGet, it automatically is updating my website web.config assembly binding redirects to older versions of System.Web.Mvc and Newtonsoft.Json. The website web.config currently has them bound to the latest version being used. Using the GUI, utilizing Manage NuGet packages for Solution... I choose to UPDATE this NuGet for applicable projects that have a reference to the old version.

I am trying to downgrade a NServiceBus dependency so instead of using 4.0.0.0 to use 2.5.0.0 I am trying with the following ways, none of which seem to work. <runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="NServiceBus" publicKeyToken="9fc386479f8a226c" culture="neutral"/> <bindingRedirect oldVersion="4.0.0.0" newVersion="2.5.0.0"/> </dependentAssembly> </assemblyBinding> </runtime> I also tried with codebase : <runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name=

Out of nowhere my ASP.NET MVC 4 solution gives me this error: Inheritance security rules violated by type: 'System.Web.WebPages.Razor.WebPageRazorHost'. Derived types must either match the security accessibility of the base type or be less accessible. I Googled the problem and everybody says it has happened when anyone updates the solution from one version to another. But I didn't update my solution, just change the IDE from VS12 to VS13. Is this what creates the problem? The full stack trace is as follows: [TypeLoadException: Inheritance security rules violated by type: System.Web.WebPages

Is it possible to include a web.config or app.config file in the azure functions folder structure to allow assembly binding redirects? Assuming you are using the latest (June'17) Visual Studio 2017 Function Tooling, I derived a somewhat-reasonable config-based solution for this following a snippet of code posted by npiasecki over on Issue #992 . It would be ideal if this were managed through the framework, but at least being configuration-driven you have a bit more change isolation. I suppose you could also use some pre-build steps or T4 templating that reconciles the versions of the nugets in

This is not a problem question but a general understanding question on assembly binding redirect's working. Queries Why binding redirect shows only major version and not minor, build and revision numbers? Does old and new version change only when there is change in major version? <dependentAssembly> <assemblyIdentity name="FooBar" publicKeyToken="32ab4ba45e0a69a1" culture="en-us" /> <bindingRedirect oldVersion="7.0.0.0" newVersion="8.0.0.0" /> </dependentAssembly> Evk Why are binding redirects needed at all? Suppose you have application A that references library B, and also library C of

This question already has an answer here: Windows update caused MVC3 and MVC4 stop working 9 answers After installing the ASP.NET MVC 3 security update KB2990942 it appears the MVC version increased from 3.0.0.0 to 3.0.0.1 . This causes Visual Studio to no longer find the reference. <Reference Include="System.Web.Mvc, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL" /> Resharper does not show any problems but the build fails with lots of unresolved MVC types and a warning: Warning : Could not resolve this reference. Could not locate the assembly