This is the best I could find on this. We followed the guidelines and things are working fairly well.

Structuring Solutions and Projects
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/tdlg_ch3.asp

BOb



>How are you all setting up your largish projects?
>
>I'm finding that especially ASP.Net projects get out of hand quite quickly in terms of size of pages involved in the system in VS net. It seems the only way to get a handle on this is to break things into seperate directories at least for ASPX pages.
>
>Beyond that though there's also the issue of reusable code. I've been trying to separate most things into separate projects that make up a solution. My current solution has about 10 projects in it and while that works reasonably well, I'm thinking this is a nightmare if I ever need to move the project or in my case share it with others. I can provide all the code for the projects and the solution, but once moved the solution will not find all the subprojects unless the directory structure for everyhing is the same on the copied machine.
>
>To make things worse with Web projects I tend to put the main Web app into a Web directory (off the Web root), while the 'worker code' (business objects and utility classes) go into a Project tree somewhere else, which results in code scattered about in multiple places. The worker code of course will often be reused in multiple projects especially the business object framework and utility classes.
>
>Any ideas on how to manage this process more fluidly?
>
>
>Sorry for the 'operational' questions - I'm getting close to the point of deployment of some tools and just looking for some food for thought to facilitate the process...