After the recent update of NuGet to version 2.7 there seem to be some issues when creating a fresh install of Piranha CMS. Luckily there's a fairly simple workaround for this issue.
The package Piranha.Core is dependent on the ASP.NET MVC package from NuGet and when installing this package with previous versions of NuGet the runtime assembly versions are added to the Web.config. After the latest upgrade this section seems to be missing even though no updates have been made to any dependent packages. This causes exceptions when starting the application as the runtime don't know which assemblies to load.
If you're experiencing these issues after having made a fresh install of Piranha CMS you should open your Web.config and verify that the following section is present. If the section is missing you should add it to your Web.config.
<runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35"
culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-184.108.40.206" newVersion="220.127.116.11" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="System.Web.WebPages" publicKeyToken="31bf3856ad364e35"
culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-18.104.22.168" newVersion="22.214.171.124" /> </dependentAssembly> </assemblyBinding> </runtime>
We have filed an issue at NuGet's repo at CodePlex and are awaiting the upcoming release which is scheduled for December. If the issue isn't resolved or we can't wait we'll try to release a work around in an upcoming release of Piranha CMS on NuGet.
blog comments powered by Disqus