Looking for a design pattern to handle asp.net sub projects -


i'd re-design site 1 asp.net solution, , project each of main areas of site. layout this:

main project

  • masterpage

-- legal section project

--- legal main page (uses main masterpage)

--- legal sub page (uses main masterpage)

-- administration section project

--- main admin (uses main masterpage)

--- second admin (uses main masterpage)

--- third admin (uses main masterpage)

the way i'd site work if menu item master page gets triggered, sub pages if in different project, able handle first, perhaps asking user save before event master page gets handled.

any samples out there that?

asp.net 2.0 or 3/3.5 fine. mvc or mvp work this?

either mvc or webforms this. have manage stuff manually in file system.

with mvc, there concept of area, out-of-the-box, areas must in same project. recommend mvc this.


Comments

Popular posts from this blog

linux - Using a Cron Job to check if my mod_wsgi / apache server is running and restart -

actionscript 3 - TweenLite does not work with object -

jQuery Ajax Render Fragments OR Whole Page -