Home/ Questions/Q 6033631
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T05:30:40+00:00

I’m working on converting some of the partial views in my MVC 3 app

  • 0

I’m working on converting some of the partial views in my MVC 3 app (which I recently converted from MVC 2, using the MS tool) from ascx to cshtml (Razor).

Simply put: I’m trying to do a Html.RenderPartial of a Razor partial view, directly from an aspx Master Page. The Razor partial view simply has “Hello World” in it — no @model or @inherits or anything. When I run my app, at this point I get the following error: “The view at …..cshtml must derive from ViewPage, ViewPage, ViewUserControl, or ViewUserControl.” In other words, it looks like it’s looking for a non-razor view.

So.. If I explicitly put “@inherits ViewUserControl” at the top of my razor partial, I get a different error: “…cshtml.Execute(): No suitable method found to override.”

I created a new MVC 3 app from scratch and tried the same thing at its simplest. An aspx master page that does a RenderPartial on a razor partial. And it works fine. But this big hairy existing app is too big to do a start from scratch.. Yet something in there is keeping this from working.

This might look like a duplicate of some other questions out there, but I’ve tried everything from the ones I’ve found. I’ve even uninstalled MVC 2 from my machine. Suggestions/help would be most welcome!

Thank you…

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Answering my own question here..

    It turns out that the MVC 2 app (which I didn’t write, btw) used a custom ViewEngine, which derived from WebFormViewEngine. When I converted my partial view to razor, I added “~/Views/Shared/Modules/{0}.cshtml” to the locations array in that class, without realizing that it’d be using the WebFormViewEngine.

    So, I ended up creating my own ViewEngine, which derives from RazorViewEngine… and added my /Modules path to that one instead. It works!

    Starting over fresh and manually converting the app to MVC 3 helped (thanks again Darin D), because it forced me to go through all the steps myself, and caused me to find this issue.

    • 0