Build Configurations in the a .NET Solution

Hi there,

I am looking at getting TeamCity for our CI needs and I want to understand which version do I need. Currently, there is a free version (the Professional Server License) and one that costs money (the Enterprise Server License). The Professional Server License works for up to 20 build configurations. We are a .Net shop and develop in Visual Studio 2013. I need to understand what goes in a build configuration. Is it a VS2013 solution, with all projects that are inside or each project in the solution will have to have its own build configuration? Our systems tend to have a lot of services that control all kinds of low level devices, plus Windows Forms/WPF GUIs and Web Applications, so one single solution tends to have more than 20 projects inside. If each project within the solution needs its own build configuration, then we need to pay for the Enterprise Server License. However, if the entire solution will be added under TeamCity as a single build configuration, that means the Professional Server License will be enough for the time being, until we reach 20 build configurations.

Thanks,
Ed

4 comments
Comment actions Permalink

Hi Eddie,

Sorry for late reply.
How to set up build configurations in TeamCity depends on your solution structure. For example, if the final product of assembly is a single object then it could be built in one build configuration. If the final product is multiple objects or if there is a code that compiled more then once during the build then it should be extracted to a separate build configuration. For example if the package created in one project should be reused in several projects, then it is recommended to create a different build configuration which publishes artifacts to NuGet Feed.
Also TeamCity Getting Started webinar could be useful for you.

0
Comment actions Permalink

Hi Alina,

One of our solution will include typically multiple projects that are built into dlls or executables. Do we need one build configuration for each separate assembly generated or one per solution will be enough?

Thanks,
Ed

0
Comment actions Permalink

Hi,

TeamCity uses solution file in the same way as any other build script. So you can have one build configuration per solution.
While as I wrote before you should decide how to set up TeamCity depending on your application logic. Also please read the answer for the related question on stackoverflow.

0
Comment actions Permalink

Thank you Alina, this truly clarifies the matterf or me. All the best.

0

Please sign in to leave a comment.