Best Practice - Build Configuration Structure?

I am wondering what is the best practice for setting up build configurations.

I have a solutions structured like this

App.sln
-AppBusiness.proj
-CommonTools.proj
-AppBusiness.Tests.proj
-CommonTools.Tests.proj

Should I pull each project and build it individually with a dedicated build configuration and use dependencies between the build configurations in team city?
Should I break my solution into smaller parts such as this? :

CommonToolsBuildConfig
-CommonTools.sln
-CommonTools.proj
-CommonTools.Tests.proj

AppBusinessBuildConfig (depends on CommonToolsBuildConfig)
-AppBusiness.sln
-AppBusiness.proj
-AppBusiness.Tests.proj
-CommonTools.proj

AppBuildConfig(depends on AppBusinessBuildConfig and CommonToolsBuildConfig)
App.sln
- AppBusiness.proj
- AppCommonTools.proj

I was planning on running unittests and code coverage as well. Is it enough to simply run the tests on the dependency builds or should I include them everywhere?

Any help would be appreciated.
Thanks.

4 comments

Use maven and it structure. It's the best practices.

0

I am using .net c# is there anything similar available for that?

0

Okay.. That's one answer.

Is it really the only answer?  What if you are in an environment (such as I am) where the tool sets are decided and Maven isn't one of them?

Curious ('cause I've been pondering the same question).

Thanks - Jon

0

Please sign in to leave a comment.