The view must derive from WebViewPage, or WebViewP

Question

I'm following Justin Slattery's Plugin Architecture tutorial and trying to adapt it for Razor, instead of WebForm Views.

Everything else (controllers, plugin assembly loading, etc) seems to be okay. However, I'm not able to get embedded Razor views to work properly. When I try to browse to the "HelloWorld/Index", I get the following error:

The view at '~/Plugins/MyProjectPlugin.dll/MyProjectPlugin.Views.HelloWorld.Index.cshtml' must derive from WebViewPage or WebViewPage<TModel>.

The exception is thrown by System.Web.Mvc.RazorView.RenderView(ViewContext viewContext, TextWriter writer, Object instance) +262

I can include the complete stack trace, if needed.

Can anyone advise as to what I might be doing wrong?

Answer 1

I had a same problem because I did not commit the packages folder which contains the razor libraries. Then I added the package, it worked but upon rebuild it broke. Then I turned off nuget automatic run upon build and now it's working fine. In my case, nuget was messing things up.

Answer 2

Note: I had an extremely similar issue and had to finally track down that I was the only developer with MVC 4.0.0.0 linked in their solution.

Everyone else had 3.0.0.0 properly referenced and was building/running without error.

TL;DR Make sure that your references are the same as the rest of your development group.

Answer 3

You may checkout the following blog post which is more adapted to Razor.

But to answer your question, since you are now serving your views from a non standard location there is no longer the ~/Views/web.config file that applies and allows you to specify the base type for your razor views. So you might need to add the following on the top of each razor view:

@inherits System.Web.Mvc.WebViewPage
@model ...

Answer 4

Install the package: Install-Package Microsoft.AspNet.WebPages

Answer 5

I want to share my pain.. site was working fine locally, however when I published to customer's IIS, it was throwing this error. All the web.config files (root and /Views) matched perfectly with a working copy of the site.

One of the views (logon.cshtml) had inconsistent line endings and I didn't click yes to fix it on my Windows machine.

Clicking yes to the inconsistent line endings dialog and publishing the logon.cshtml view fixed it for me.

Answer 6

I got this error when I tried to add MVC scaffolding (specifically the Views folder) to a Web API project. Darin Dimitrov's answer says:

there is no longer the ~/Views/web.config file that applies and allows you to specify the base type for your razor views

And in comments on that answer, joelnet said:

I was able to copy the web.config from ~/Views to my alternate location to solve my issue with this.

and Paul d'Aoust said:

If you're having trouble getting the solution in @joelnet's comment to work, try cleaning and rebuilding the project.

These hints helped me figure out the solution.

First I copied the Web.config from the Views folder of another project in the same solution to my new Views folder. I renamed the main namespace tag to match the new project, and after getting an error removed another <add namespace="..." /> that I didn't need. I then triggered a build (only a normal build, I didn't need to clean and rebuild), and I was able to load my new view without errors.