I have spent a lot of time over the past few months on this. Here are my observations.
Good / Easy - Getting Webforms to be Webforms in MVC Controllers - It was great to just get on a new MVC3 project and drop Webforms pages. - I managed to move the <pages><controls></controls></pages> section to the <pages><controls></controls></pages> directory in the new web.config there
Dirty / difficult
this is what i did to solve this problem
@if (System.Diagnostics.Debugger.IsAttached) { <script src="../../Scripts/Mvc3/jquery-1.7-vsdoc.js" type="text/javascript"></script> @* intellisense! *@ @Html.RelativeJavascript(Links.Scripts.Mvc3.jquery_1_7_js) @Html.RelativeJavascript(Links.Scripts.Mvc3.jquery_unobtrusive_ajax_js) } else { @Html.RelativeJavascript(Links.Scripts.Mvc3.jquery_1_7_min_js) @Html.RelativeJavascript(Links.Scripts.Mvc3.jquery_unobtrusive_ajax_min_js) }
Recommendations:
- Use
T4MVC in all cases, even if you are pure web forms. The output of magic strings for static content ( .js , .css , images specifying patterns) is outstanding.
Maslow
source share