Unzip the BuildSamples.zip file to C:\
There is a zip file called BuildSamples.zip that was installed when you installed the Release Manager web application. This is installed into the web site's subdirectory named "Docs". So the default full file path of the file would be C:\inetpub\wwwroot\ReleaseManager\Docs\BuildSamples.zip. Your path may be different depending on where you installed the Release Manager web application.
Once you fiind the BuildSamples.zip file containing the sample directories and setup files unzip it to C:\. If you can't use C:\ you will have to change some config files in the last step of these instructions.
Note the subdirectories under the C:\BuildSamples directory you just created - they will be used in the reset of the steps need to setup the buld sample.
Under the C:\BuildSamples\Setup directory you will find 2 subdirectories CCNetConfigFiles32Bit and CCNetConfigFiles64Bit. If you are on a 32 bit Windows version you would copy the contents of CCNetConfigFiles32Bit to the "server" subdirectory under you CruiseControl.NET program directory. So the default for 32 bit Windows is to copy C:\BuildSamples\Setup\CCNetConfigFiles32Bit to C:\Program Files\CruiseControl.NET\server.
The default for a 64 bit version of Windows would be to copy C:\BuilSamples\Setup\CCNetConfigFiles64Bit to C:\Program Files (x86)\CruiseControl.NET\server.
Apply the file C:\BuildSamples\Setup\Northwind.SQL to your Release Manager database to make the Northwind project. The default database name is ReleaseManager and this is sometimes created through a wizard when you first open the Release Manager web application.
From the Release Manager web application edit the Northwind project to make any changes that might be needed because your environment is different than the default.
The second step of the project wizard is where you setup the URL's to point to you Subversion repository. If you didn't install the BuildSamples.zip to C:\ you will have to change the Subversion URL's to point to your directory.
The third step of the project wizard contains a connection string to a sample bug tracking table. This table is in your Release Manager database. So if your Release Manager connection string is not the default of "Provider=SQLOLEDB;Data Source=localhost;Initial Catalog=ReleaseManager;Integrated Security=SSPI" then you need to change it in the wizard. You can test the connection if you make any changes.
Make sure if you made any change to the Northwind project using the wizard that you go to the last step, Finish, and click the "Save Project" button.
Optionally create a sample development database, NorthwindDev, and a sample Test environment database NorthwindTest on your database server. Once created you will need to grant rights to the IIS identity to these database like you did when you setup the ReleaseManger database. You can look to the ReleaseManager database to see which acccount was granted rights there.
If your connection strings are not the defaults, you will need to change them in a few places. First if the connection string for NorthwindDev is not the default you will have to change the file: c:\BuildSamples\Development\Northwind\Web\3.3\Northwind\Support\Config\WebEnvironment.config
If the connection string for NorthwindTest is not the default you will have to change it in 2 files: c:\BuildSamples\NorthwindTest\Support\Config\WebEnvironment.config
And change the variable "TargetConnectionString" in this file c:\BuildSamples\Builds\Tools\MSBuild\Default.proj
Setup the web site NorthwindTest in IIS. The default is open the IIS manager and under Web Sites/Default Web Site create a new virtual directory called Northwindunder. It's Alias should be set to NorthwindTest and it's path should be C:\BuildSamples\NorthwindTest.
Once the virtual directory is created check that it's properties are correct. You usually get to the properties by right clicking the virtual directory and selecting Properties. The Documents tab should have a "Default.aspx" as it's default content page. The ASP.NET tab should have the ASP.NET version set to 2.0.50727 or greater.
Still in Properties, click the Directory Security tab and click Edit. Note the identity used for Anonymous Access and authentication control. Give this identiy full rights under C:\BuildSample\ by right clicking that directory, selecting Properties and then selecting the Security tab.
Optionally you could setup another IIS web site that allows browsing in the path C:\BuildSamples\Builds\ReleaseManagerOutput
Install the ReleaseManager TortoiseSVN Plug-in. This is done by running the RMTClientSetup.msi. You may have already done this. Detailed instructions are found under the "Help"option in you Release Manager web application.
Set the ReleaseManager TortoiseSVN Plug-in to work with the directories C:\BuildSamples\Development\Northwind\DB and C:\BuildSamples\Development\Northwind\Web
You setup should look like this right before you save the second plugin setup.
If you didn't install the Northwind sample files to C:\BuildSamples then go to the directory that you did install it to and search for the text string C:\BuildSamples and change C:\BuildSamples to whatever directory you did install it to.
Do the same for all .config files under your C:\Program Files\CruiseControl.NET\server directory.
You now have the Northwind Sample project installed.