Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8913341
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 15, 20262026-06-15T04:26:10+00:00 2026-06-15T04:26:10+00:00

After upgrading to ASP.NET MVC 4, application is breaking on accessing any webpage defined

  • 0

After upgrading to ASP.NET MVC 4, application is breaking on accessing any webpage defined inside an Area

Error screen shot

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: An error occurred creating the configuration section handler for system.web.webPages.razor/host: The given assembly name or codebase was invalid. (Exception from HRESULT: 0x80131047)

<section name="host" type="System.Web.WebPages.Razor.Configuration.HostSection, System.Web.WebPages.Razor, Version=__WebPagesVersion__.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" />
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-15T04:26:12+00:00Added an answer on June 15, 2026 at 4:26 am

    Added this as an answer from comment:

    Change Version=_WebPagesVersion_.0.0 to Version=2.0.0.0

    Alternatively see if you have any other web.config files floating about in your project and see what values are used there – I understand that sometimes if you have multiple web.config referencing different version of the hosts section it can get quite upset. BTW there is no need to uninstall MVC 3 before 4 – they co-exist happily!

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

After upgrading to my ASP.NET MVC 4 Developer Preview assemblies to the latest MVC
After manually upgrading an ASP.NET MVC project to MVC4 using these instructions , how
I am getting below error when after uploading my asp.net application on window server
We're busy upgrading an ASP.NET MVC 2 Application using the 3.5 framework to an
I have a ASP.NET MVC 4 application with Web API. It's working great. But
We have a Com+ VB6 DLL used in our asp classic application. After upgrading
After upgrading my ASP MVC from 3 Preview to 3 Beta I see strange
Initially, after upgrading to ASP.Net 4.0, I was receiving request validation errors, which I
I had no problems using NHaml with ASP.NET MVC Beta, but when upgrading to
After upgrading node to v0.8.1, bundled Meteor apps now throw an error: node: symbol

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.