Last post Aug 27, 2013 07:15 PM by Kaelum
Aug 07, 2013 05:44 PM|Cheng Bao|LINK
I got following warning when build my solution
Consider app.config remapping of assembly "WebGrease, Culture=neutral, PublicKeyToken=31bf3856ad364e35" from Version "184.108.40.206"  to Version "220.127.116.11" [*\WebGrease.1.3.0\lib\WebGrease.dll] to solve conflict and get rid of warning.
I have followling line in web.config
<assemblyIdentity name="WebGrease" publicKeyToken="31bf3856ad364e35" />
<bindingRedirect oldVersion="0.0.0.0-18.104.22.168" newVersion="22.214.171.124" />
Aug 09, 2013 03:21 AM|Shawn - MSFT|LINK
For this situation, this packages must be uninstalled and reinstalled to solve the problem, below is the reason which you could refer to:
The reason packages must be uninstalled and reinstalled is:
For further information, you could access to:
Besides, you could get more information by refering to the below links:
Aug 09, 2013 12:01 PM|Cheng Bao|LINK
It is pretty weired to me. I tried reinstall all packages through nuGet console, before post here to get help.
after that, not only webgrease report warning, other packages like System.Web.MVC reports same warning too, so I created this thread.
And I tried to delete /bin and /obj, restart VS2012 nothing helps.
Today, I delete /bin and /obj again, restart VS2012, now the warning is gone.
Thanks for helps, If it comes back again, I will definely try your suggestions
Aug 14, 2013 08:11 AM|Shawn - MSFT|LINK
For this situation, it is very appreciated to share your solution to us, though it may be a temporary solution. It will be helpful for others, and welcome to post your question on this forum, if you encounter an issue in your future programming.
Aug 27, 2013 07:15 PM|Kaelum|LINK
There is an incompatability within the current NuGet packages for at least 2 of the items installed for ASP.NET MVC 4 when you update the packages to the current releases. I don't remember exactly which ones are causing the issue, but one package only works
with WebGrease 1.3.0 and the other requires 1.5.2, which causes the conflict. I went through all the steps to remove everything and then re-install, twice, and the second time I didn't install the offending update, but I don't remember what it was. I also
had to manually update the web.config to bind the 1.3.0 version and not the 1.5.2, as the latter does not work. It causes build warnings and flat out fails to run if you try.