View Errors Migrating WebForms To ASP.NET MVC Pattern

I’ve been working a project where we had a really solid WebForms application, but wanted to utilized ASP.NET MVC and more client side programming.  We created some partial views used by some controllers and kept getting this error “The name 'Model' does not exist in the current context”.  It turns out that the the Views folder needs a web.config file underneath it.  The easiest way to do this is to copy a web.config from the Views folder in a template project of a MVC web app.

1 comment: