I think it's a good idea to separate things the way you're doing. Your projects should be separated by functionality, IMO, because they become separate .DLLs. Anyway, the way we manage that (in terms of sharing between solutions, etc.) is with SourceSafe. You can share files between VSS projects, so that keeps the source code in one place on VSS, but you may end up using it in multiple places on your PC. IOW, say you have the same DataAccess project that you want to use in both a WinForm app and a WebApp. In VSS, you simply share the files between the two solutions.

BTW, 10 projects in a solution is nothing ... we have that many in just the BizObjects alone! So far, our WinForm solution has over 50 projects. The WebForm solution is smaller, only 30 so far, 20 of which are shared between Win and Web (business and data access components). And we're not done with either yet ... I expect we'll be adding more.

So, some sort of Source Control seems to be the answer to managing large solutions.

~~Bonnie


>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...