Which CI is suitable for .Net

Question

I want to automate the assembly process of my company. We use the Net.Net platform for software development and currently use VisualSourceSafe as a control source.

So, I want to know which tools are the best CI for the .NET platform.

Based on my searches, I found that CrouseControl.Net is better than others, so what do you think.

note: I also ask a question about: integrating Sourcesafe with the CI tool , but this is different from this question.

TeamCity - CrouseControl.Net - or etc.

Answer 1

This question has answers comparing cruisecontrol.net and teamcity.

Personally, I was very pleased with Teamcity. I used cc.net for many years, but TeamCity worked better for me.

A long list of continuous integration options is on Wikipedia

Answer 2

"Best" is very subjective.

If you want to get up and work quickly, TeamCity is the way forward IMO. Its control panel user interface also removes stains from the CruiseControl.NET user interface.

CC.NET requires very little manual configuration of the XML configuration, etc., but as soon as the configuration is quite enjoyable and, of course, free. TeamCity is free for up to 10 developers or so.

Answer 3

TFS 2010;) Integrated source code management, assembly system, document repository, reporting, work item tracking and, most importantly, .NET assembly.

Answer 4

from The Art of Unit Testing with Examples in a .NET book - Chapter 6

• CruiseControl.NET ( www.cruisecontrolnet.org )
• TeamCity ( jetbrains.com/teamcity/ )
• NAnt ( nant.sourceforge.net )
• MSBuild ( http://msdn.microsoft.com/en-us/library/wea2sca5 (VS.80) .aspx )
• FinalBuilder ( www.FinalBuilder.com )
• Visual Build Pro ( www.kinook.com )
• Visual Studio Team Foundation Server ( http://msdn.microsoft.com/en-us/vstudio/ff637362.aspx )

One popular continuous integration tool is CruiseControl.NET . it is a fully open source and supports the idea of tasks that are individual commands that are executed during the build, and the concept of triggers , which can automatically trigger the build when certain events occur, such as version control updates.

Among commercial tools , Visual Studio Team System 2008 supports automated builds and continuous integration out of the box. If this is a little over your budget, look at FinalBuilder and Visual Build Pro. These two commercial and highly successful build tools allow visual editing and maintenance of automated build projects. Which means simplifying the maintenance of the assembly file, which can be quite scary for large projects.