IntroductionJetBrains TeamCity

In the previous parts of the TeamCity series I discussed how you can configure the TeamCity CI build server to run unit tests and how you can make this all happen using a MSBuild script.

The end goal of this series is to arrive at a build configuration which we can use to automatically deploy an ASP.NET MVC web application. We want a reliable way of deploying an application to a new environment (staging, acceptance, production…etc.). Manually copying files, editing configuration files, synchronizing servers…is not a wise course.

You want to should avoid manual actions during deployment. Sure, you can get all the steps correct, but in the long run mistakes are unavoidable. And besides, doing all this stuff manually is just plain boring and tedious.

One of the first steps in deploying an ASP.NET / ASP.NET MVC application is to make sure its configuration file (Web.config) is transformed so it fits the environment in which the application will be running. Let’s see how we can apply Web.config transformation using TeamCity.

Read the rest of this entry »

IntroductionJetBrains TeamCity

This post picks up where the previous post, Running Unit Tests With TeamCity, left off. If you haven’t read it yet, read it first.

The first post in this series showed how you can run unit tests (using NUnit) in TeamCity by creating a build configuration and configuring two build steps, namely:

  1. Compile the code using the MSBuild build runner
  2. Run the unit tests using the NUnit build runner

This post shows how you can replace both of these steps by one single step which executes all of these actions using a MSBuild script.

Read the rest of this entry »


Get every new post delivered to your Inbox.

Join 341 other followers