How to use Subversion , nant & cruise - go build server to achieve continuous integration of .net projects
Use subversion as source code repository. All working code goes inside /trunk folder. Set Cruise- Go server to continuously poll subversion server for modification and if it senses change, then cruise agent pull all the code. You can do this through setting pipeline in cruise configuration file.
NANT build script themselves are part of source code so they gets pulled in whenever cruise agent download source code. It means build script themselves are version controlled ;)
Build scripts then run tasks as specified in cruise configuration files (pipeline configuration), usually compile project , run unit tests , copy correct configuration files based on environment name parameter (dev , qa , live) and then copy them to target folder.
QA server disk must be accessible to cruise agents - thus it can push latest changes & configuration files as soon as source code is changed on svn. These folders on QA server are also mapped to IIS web sites.
This way QA websites are continuously updated with code changes, asset files, configuration files.
Heres diagram :
