I have an internal NuGet package containing one dll, no external dependencies of the NuGet package and web.config conversions.
However, when I run the Update-Package for my projects (lib class and website) for that particular NuGet, it automatically updates my website. binding bindings of the web.config assembly to versions older than System.Web.Mvc and Newtonsoft.Json. The web.config website is currently tied to the latest version used.
Using the GUI, using the NuGet package management packages to solve ... I am choosing to UPDATE this NuGet for applicable projects that reference the old version. Then select Update
Here is the result from the package manager: http://pastebin.com/3ySwTRFR
And my web.config switched from:
<dependentAssembly> <assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" /> <bindingRedirect oldVersion="0.0.0.0-5.1.0.0" newVersion="5.1.0.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" /> </dependentAssembly>
To:
<dependentAssembly> <assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" /> <bindingRedirect oldVersion="0.0.0.0-4.0.0.1" newVersion="4.0.0.1" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-4.5.0.0" newVersion="4.5.0.0" /> </dependentAssembly>
In the NuGet package that I am updating, there is a dll that references Newtonsoft.Json (but does not explicitly make the NuGet package dependent)
When an unknowing developer updates this NuGet package, he interrupts the working environment by looking for an old version of the MVC DLL or JSON.NET.
In the past, I tried to use - IgnoreDependencies powershell command switch , but this does not seem to affect the problem.
Any idea on what can transform my web.configs (without explicit conversion) in a service pack?
Edit: VS2015 w / NuGet 3.3.0 seems to behave better ... during a random package update, he discovered that the old BAD binding redirects and fixes it! 
felickz
source share