tag:blogger.com,1999:blog-35403832.post2392595464482695680..comments2009-05-01T11:05:27.100+02:00Marnixhttp://www.blogger.com/profile/00913090261390882195noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-35403832.post-23171857571197736782009-05-01T11:05:00.000+02:002009-05-01T11:05:00.000+02:00Hi,<br /><br />Thanks for the tip. <br />The article you're referring to is not quite the same thing; it describes how webforms and MVC can co-exist using routing. The solution I'm proposing here allows you to mix assets from WebForms based applications with MVC; it enables you to use MVC controllers with webforms controls in ways not supported by MVC itself. <br />This solution enables the controller to dictate which partial views (or controls) are to be loaded into what content template in a master page. This is a different way of constructing views compared to MVC's hierarchical views.<br /><br />I'm using this solution for new developments on existing sites. It allows me to reuse existing controls developed for webforms-based pages while developing new functionality using MVC.Marnixhttp://www.blogger.com/profile/00913090261390882195noreply@blogger.comtag:blogger.com,1999:blog-35403832.post-29525033147323267622009-05-01T03:32:00.000+02:002009-05-01T03:32:00.000+02:00Have a look at this. It would seem you don't have to go to the trouble of what your describing....<br /><br />http://www.packtpub.com/article/mixing-asp.net-webforms-and-asp.net-mvcvdhanthttp://www.blogger.com/profile/01571747248983032083noreply@blogger.com