I have an external ASP.NET MVC 1.0 interface that works well, and the functions as part of it are the dynamic data section, which I use as the internal admin area for the site.
I haven't confused authentication too much yet, but it seems like a pretty logical website design for any new .NET sites that are going these days. I hope that someone can have some tips to share how to block the "Dynamic Data" section of the site (Dynamic Data uses simple old ASPX pages) using the "Track Authentication" function, leaving freely visible components of the MVC frontend.
The FYI site is hosted on Win2k3 / IIS6.0, and there is no MVC installed on the server, so I include the DLLs in the \ bin directory and use the routing mechanism to add .aspx suffx to the controllers, since IIS can understand parts of the MVC site.
Thanks...
Bernard.
source
share