Say you have a large website that contains several discrete applications that run on the same site to do different things. You do not want to manage everything as a single project, so you break them into pieces, work on them in complete isolation from each other, and simply deploy them separately in one runtime environment.
These applications will work in the same process. No virtual directories or application isolation. They will share things like session, cache, cookies, etc.
Undoubtedly, the code behind and class libraries are just DLLs in the bin folder, but what is it at the level of the presentation level that should be integrated into the runtime? How about sharing the code level resources I mentioned above - cookies, session, cache, etc.? What about base page classes?
Example: it seems to me that each supporting application should be a “main page” - it needs to know where the main page will be located and which ContentPlaceHolders are available, because sub-application web forms will be needed to link to this material.
Any other thoughts here? Suppose sub-applications share the same main page, theme, and everything else at the presentation level, so they seem to be a fully integrated part of the whole. But they will work in different Visual Studio projects by different teams of developers who do not know anything about each other, besides what is absolutely necessary.
Anyone want to share some recommendations here?
Deane source
share