tags:

views:

35

answers:

0

Hi - we have more than 30 projects and 7 web project solutions.

In our current build architecture, out of 30 projects about 20 projects constitute the app, db and other lower level layer projects and are being used by the remaining 7-8 web layer projects.

Web projects have each of the lower level projects as project reference and in order to build the complete website, we have to build every web solution(lets have the count as 7) once, which inturn means we are building same projects referenced (lets say 20) 7 times (7*20).

This increases the build time. But if the lower level projects are used as dll reference, they can be built once and each web project doesn't need to build them each time. Does this make sense? I'm confused if it's a good idea to use a dll reference in a huge project.

Is there any particular reason project reference is better than dll reference and vice versa?

Please give me some suggestions.

Thanks!