tags:

views:

176

answers:

5

I want to create an ASP.NET build server for the first time since I've never used it.

Does anyone have a tutorial or resource on how to make an ASP.NET build server?

Or can anyone tell me how it's done?

+5  A: 

If you by "create" mean "setup a build server" then I suggest you take a look at TeamCity from jetBrains.

TeamCity is a multi purpose build server and can be used to build ASP.NET projects as well.

You can get up and running for free, and its very easy to set up, compared to CruiseControl.Net.

Take a look at MSBuild to see how to do specific ASP.NET build stuff.

Oh, and if you really want to create your own build server from scratch (but why?), I can't help you.

Christian Dalager
+3  A: 

You could make a build server using CruiseControl.NET ? which can build your project.

CruiseControl.Net Tutorial – Part 1

CruiseControl.Net Tutorial – Part 2

There us no asp.net build server as such.

abmv
+2  A: 

Do you have a one-click build script? If not, you should create that first. Once you are able to run a single command and get a complete build, then it is easy to set up CruiseControl or some other build server.

Josh Yeager
A: 

Given the strength of the build servers out there it's really not sensible to spend any time developing your own.

You will, however, need at the minimum

  • a one-click build script
  • a source code repository (e.g. Subversion, TFS, or even [shudder] SourceSafe)
  • a server to use as a build box (I use a virtual image)

You may also find a one-click deployment script written using something like Powershell to be useful, too.

Note that a very effective alternative to CruiseControl.NET and TeamCity is Hudson. Although it's written in Java it's ridiculously simple to get going with a J2EE server like Tomcat.

The key strength of Hudson is the range the plug-ins, which allow you to monitor most version control systems and then not just build (through MSBuild or even the command line) but also run unit tests, acceptance tests, and so on.

Jeremy McGee
Beware, I'd almost downvote just for mentioning sourcesafe ;-)
jeroenh
A: 

You might look at Web Deployment Projects -- they allow you to build your site and merge all DLLs into a single file, for a fully pre-compiled site. You can use it with MSBuild.

An option on the automation side is Team Foundation Server's (TFS) automated builds. TFS also includes source control, bug tracking and many other features you may or may not need.

RickNZ