I was looking for a solution to break up a large enterprise web application into smaller, more manageable modules and the ability to create and deploy separate subprojects, while at the same time, each of the subprojects inherits from the common set of resources such as the main page, the parent class of the page, app_code, css and etc.
I found a workaround to configure this in VS 2005/2008. in Visual Web Developer Blog Post .
Question: is there a new approach to solving this problem in VS 2010 (apparently the same workaround mentioned above does not work for VS2010). Or maybe I'm generally following the wrong road; although it makes sense to me that this would be the desired way to configure large enterprise applications if it weren’t for an industry standard or best practice?
Your help and comments are appreciated.
Thank.
source
share