4

I want to Automate the build process of my company. We are Using.Net platform for developing softwares and currently using VisualSourceSafe as source control.

So I want to know that which tools is the best CI for .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 a CI tool but that's different than this question.

TeamCity - CrouseControl.Net - or etc

Community
  • 1
  • 1
Nasser Hadjloo
  • 12,312
  • 15
  • 69
  • 100
  • 2
    Don't forget Hudson! It's free AND awesome. There are a ton of plugins, including Visual SourceNotSoSafe. That it's written in Java doesn't preclude you from building .NET projects with it. – Christopher Orr Mar 07 '10 at 11:59

4 Answers4

2

This question has answers that compare cruisecontrol.net and teamcity.

Personally, I have been very happy with Teamcity. I used cc.net for years, but TeamCity has worked better for me.

A long list of continuous integration options is at Wikipedia

Community
  • 1
  • 1
Mike Two
  • 44,935
  • 9
  • 80
  • 96
  • @Mike - thanks for question, I'm also looking for other option CC.net and TeamCity are good but is there any third option which could be used ? – Nasser Hadjloo Mar 07 '10 at 07:51
  • @Nasser Hajiloo - yes there are several options. I have not used any of the others so I don't feel comfortable comparing them, but I will list some that I know of. – Mike Two Mar 07 '10 at 07:57
1

"Best" is very subjective.

If you want to get up and running quickly, TeamCity is the way forward IMO. Its dashboard UI also knocks spots off of CruiseControl.NET's user interface.

CC.NET requires quite a bit of manual XML configuration setup etc., but once setup it's quite nice, and of course is free. TeamCity is free for up to 10 developers or so.

Wim
  • 11,998
  • 1
  • 34
  • 57
1

TFS 2010 ;) Integrated source control, build system, document repository, reporting, work item tracking, and best of all: build for .NET

TomTom
  • 61,059
  • 10
  • 88
  • 148
0

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

One popular continuous integration tool is CruiseControl.NET. It’s fully open source and supports both the idea of tasks, which are individual commands that are run during a build, and the concept of triggers, which can start a build automatically when certain events occur, such as source control updates.

Among the commercial tools, Visual Studio Team System 2008 supports automated builds and continuous integration out of the box. If that’s a bit beyond 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. That means easier maintenance of the build file, which can get pretty scary for larger projects.

Iman
  • 17,932
  • 6
  • 80
  • 90