November Happy Hour will be moved to Thursday December 5th.

Eric
Oct 16, 2014
  43827
(2 votes)

Problem with web.config after upgrade between MVC 4 and MVC 5, 5.2.0.0 and 3.0.0.0 and missing intellisense in Visual Studio.

This one will be a short blog post but I somehow a bit related to my last post about version of MVC and the 404 handlar from BVN Networks.

I recently created a new project and updated all nuget packages to the latest version of both EPiServer and Nugets from Microsoft.

After the upgrade I could not get the site to start and I got a strange error message. I also had problem with intellisense and none of the old ways of fixing the intellisense problem seemed to help.

The first error:

[A]System.Web.WebPages.Razor.Configuration.HostSection cannot be cast to 
[B]System.Web.WebPages.Razor.Configuration.HostSection. 
Type A originates from 'System.Web.WebPages.Razor, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' in the context 'Default' at location 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Web.WebPages.Razor\v4.0_2.0.0.0__31bf3856ad364e35\System.Web.WebPages.Razor.dll'. 
Type B originates from 'System.Web.WebPages.Razor, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' in the context 'Default' at location 'C:\Users\MyName\AppData\Local\Temp\Temporary ASP.NET Files\root\63e7ff36\a1cb775d\assembly\dl3\8f568c18\9b7ddacf_d04dcf01\System.Web.WebPages.Razor.dll'.

 

This is casued by wrong versionnumbers in your config-files. This is easy to fix.

The fix:

 

      <dependentAssembly>
        <assemblyIdentity name="System.Web.Mvc"
                          publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="0.0.0.0-5.2.2.0"
                         newVersion="5.2.2.0" />
      </dependentAssembly>
<appSettings>
    <add key="webpages:Version"
         value="3.0.0.0" />

...
</appSettings>

 

The intellisense error for razorpages:

To fix the intellisense problem we need to update another web.config. This is located in the views-folder. If you look into this folder you will find out that you will need to fix other assembly versions as well:

In a view you will get the this problem with intellisens for helpers and types pages. Also the @model declaration is not working.

 

You need to change the following to target 3.0.0.0 as below

    <sectionGroup name="system.web.webPages.razor"
                  type="System.Web.WebPages.Razor.Configuration.RazorWebSectionGroup, System.Web.WebPages.Razor, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
      <section name="host"
               type="System.Web.WebPages.Razor.Configuration.HostSection, System.Web.WebPages.Razor, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"
               requirePermission="false" />
      <section name="pages"
               type="System.Web.WebPages.Razor.Configuration.RazorPagesSection, System.Web.WebPages.Razor, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"
               requirePermission="false" />
    </sectionGroup>

 

To get the intellisense to work properly you also need to change to the latest version as below:

  <host factoryType="System.Web.Mvc.MvcWebRazorHostFactory, System.Web.Mvc, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
  

If you need further assistance you can follow this post about upgrade an mvc project.

Update:

The old url did not work

References: http://www.asp.net/mvc/overview/releases/how-to-upgrade-an-aspnet-mvc-4-and-web-api-project-to-aspnet-mvc-5-and-web-api-2

Oct 16, 2014

Comments

Oct 22, 2014 09:01 AM

The URL to the asp.NET site does not seem to work.

Edit: Seems like they have withdrawn this page since I get the same page as a top hit on Google which results in a 404.

Eric
Eric Oct 22, 2014 09:34 AM

Ok, strange. Yes it looks like they have removed the page. I also get the top result in google for this page.. Maybe they have fixed the nuget update to actually fix all configs as well.

Edit: Found the page at http://www.asp.net/mvc/overview/releases/how-to-upgrade-an-aspnet-mvc-4-and-web-api-project-to-aspnet-mvc-5-and-web-api-2

Jun 5, 2015 05:02 PM

thanks a lot eric, it soloved my issue.

Jun 23, 2015 10:51 AM

You are a lifesaver! Thanks a lot :)

Tibor Mohr
Tibor Mohr Feb 9, 2017 11:38 AM

Thanks :)

Eric
Eric Feb 9, 2017 01:54 PM

You are welcome :) 

Please login to comment.
Latest blogs
AsyncHelper can be considered harmful

.NET developers have been in the transition to move from synchronous APIs to asynchronous API. That was boosted a lot by await/async keyword of C#...

Quan Mai | Dec 4, 2024 | Syndicated blog

The search for dictionary key

Recently I helped to chase down a ghost (and you might be surprised to know that I, for most part, spend hours to be a ghostbuster, it could be fun...

Quan Mai | Dec 4, 2024 | Syndicated blog

Shared optimizely cart between non-optimizley front end site

E-commerce ecosystems often demand a seamless shopping experience where users can shop across multiple sites using a single cart. Sharing a cart...

PuneetGarg | Dec 3, 2024

CMS Core 12.22.0 delisted from Nuget feed

We have decided to delist version 12.22.0 of the CMS Core packages from our Nuget feed, following the discovery of a bug that affects rendering of...

Magnus Rahl | Dec 3, 2024