I asked a similar question a while ago... but didn't really get much input. I'm sure there is much room for improvement in our current process but it seems to work OK.
- All webparts use separate Visual Studio Projects
- Utility classes use separate Visual Studio Projects
- We use a LOT of Visual Studio Solutions. We've only recently started using Solutions with many Projects inside. Some of the solutions use the same projects (ex: the solution for ProductA may use UtilsLibrary as well as the solution for ProductB). We used to only have one project per solution but found it very hard to manage dependencies.
- One "build" solution that manages all the release artifacts. We still do it the old fashioned way. This helps mitigate the risk of a "broken build" because there is an extra step to move your release DLL into the build. However, this does require more work.
