At work, we created our own ASP.NET web portal (very similar to iGoogle). We have “Applications” (stand-alone, large web forms) and “Modules” (similar to Google gadgets).
We are currently using a single solution model. Right now we have:
- 3 main projects
- 60 application projects
- 80 module projects
In order to reduce the number of copies and paste between projects, we are going to divide the general functionality (Data Access, Business Logic) into separate projects. I would also like to introduce Unit Tests, which will further increase the number of projects.
We have already reached the point at which Visual Studio is choking on the number of projects. Usually we upload only 3 main projects, and then any application / module project that we are working on.
Can a different decision structure help us? Our number of projects will only increase.
In general, an application or module refers only to 3 major projects. Soon, applications / modules can start referencing Data Access / Business Logic projects. But in general, applications and modules do not link to each other.
So, to understand what is the best practice for a decision structure when there are many projects that use a small number of core projects?
source
share