26.04.2015 Views

Team Development with Visual Studio Team Foundation Server

Team Development with Visual Studio Team Foundation Server

Team Development with Visual Studio Team Foundation Server

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

1. Open a command prompt and navigate to the following location C:\Program<br />

Files\Microsoft <strong>Visual</strong> <strong>Studio</strong> 2005 <strong>Team</strong> <strong>Foundation</strong> <strong>Server</strong>\TF Setup\<br />

2. Run the following command<br />

Bissubscribe /eventType CheckinEvent /address http://TFSRTM:8080/ci/notify.asmx /deliveryType Soap<br />

/domain http://TFSRTM:8080<br />

3. If you get any errors, or if you want to confirm that you have registered correctly, do<br />

the following:<br />

a. Open Microsoft SQL <strong>Server</strong> Management <strong>Studio</strong>.<br />

b. Open the tfsIntegration database.<br />

c. Open the tbl_subscription table.<br />

The table has entries for all events that have already been subscribed; you should<br />

be able to find the entry for CI solution subscribed to the CheckinEvent event. If<br />

required, you can unsubscribe any registered event, by simply deleting the entry<br />

from the table.<br />

Step 5 – Test the Continuous Integration Build<br />

In this step, you verify that the CI build is working correctly.<br />

1. Open the Windows Forms Application that was created in Step 1.<br />

2. Make some nominal changes to the code. Be careful to ensure that the changes will<br />

not break the build.<br />

3. Check-in the code changes you made.<br />

4. If you have access to the build machine, open Task Manager and look at the<br />

machine’s CPU usage; it should increase soon after the check-in to indicate that a<br />

build is occurring. If you look at the process list, you should see msbuild, csc, and/or<br />

aspnet_compiler using up CPU cycles, indicating that the build is in progress.<br />

5. Give the build time to run and then in the <strong>Team</strong> Explorer, double-click on All Build<br />

Types and look for the build after it completes.<br />

Trouble shooting<br />

In case the build does not show up in the build list, you can troubleshoot the problem as<br />

follows:<br />

1. Make sure that the event is subscribed correctly. For more information, see sub-step 3<br />

of Step 4 above.<br />

2. Make sure that the CI Web Application’s Web.config is configured correctly, for<br />

more information, see Step 3 above.<br />

3. Make sure that the CI Web application is running in the right context and that it has<br />

access to the TFS server.<br />

4. If you have followed the preceding troubleshooting steps but the build still fails you<br />

can debug the CI Web application as follows:<br />

a. Create a new Web site project.<br />

b. Select to add an existing Web site to this new project.<br />

c. Click the local IIS button and then select the CI Web Application from the<br />

list.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!