ASP.NET Webapplication design with "Subwebs"

Question

Can anybody give me hints and help how a large ASP.NET webapplication can be structured / designed with "subwebs" !? In other words I want to structure a large web-application where I have a solution with more web-application projects. These projects are more or less independent "modules". One project should be a kind of frame application with shared masterpages, a shared sitemap/navigataion and and a shared cental authentication. Later it should also be maybe possible also to integrate loosely older websites (which where written in classic ASP. ASP.NET 1.1, ASP.NET 2.0), but this not so important at the moment,

Answer 1

Here is the link that might help you.

http://weblogs.asp.net/scottgu/archive/2006/08/16/Tip_2F00_Trick_3A00_-Creating-Sub_2D00_Web-Projects-using-the-VS-2005-Web-Application-Project-Option.aspx

Still I would recommend you that crate multilayer application and create a high performance database layer using Microsoft Enterprise Library.

We are having huge project in asp.net contains almost 17 projects but still performance is good.