Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I want to set up a continuous integration / build server for a C# ASP.net MVC project. I’m aware of cruise control.net, what other build servers are out there and what are the advantages or disadvantages of each?
Is there any particular one that is generally considered the one to have?
We are building a lot of things with Cruise Control, including MVC projects. Cruise control is the default choice. I wouldn’t call it easy to use, but it will do what you need.
We are very tempted by Team City. It is much easier to use, but we’d need to shell out of the Enterprise edition.
We happily abandon TFS Build (2005) a year ago. Poor support for chained builds, mysterious configuration, and licensing which made it prohibitively expensive to scale. We still use TFS for source control.
Whatever you choose, keep as much of your build process in standard msbuild files as possible. If you do, you can change your build server later.