Team Build Muscleman

The main reason to do Continuous integration builds is to know when something broke the application. You can add test list to the build project and have them run everytime you build the app.
2008 enhancements - Build Explorer and Build Notifications
To override setting in Build projects, use the .rsp file and put the changes you want in there, or go further and build at command line and put changes in command line
- Warning need to control how many builds you keep or they will start to take up considerable amount of disk space
- Can use the SDC tools to repopulate ad DB on Deploy if desired
- IF using SDC, add to project so you can add to source control
- use message text ="" So you can search build out put as build output can be thousands of lines long
- in target dependsontarget="section" tag To run

1st before this target
- Highly recommend TFSSideKicks (Attrice.com)
- 2005 builds will not seamless migrate to 2008.. They will need modifications
- Use Custom build steps so you get feedback when a part of the build is running
- Keep Test in Different projec, but same solution in Source control, this will make it so you can run them when you build
- They reccomend not team building to production, but it is ok to do dev and QA
- WIX (Windowsn installer for XML)
- WIX protects are another type of Project in VS
- use this to build MSi's
- Its an addon, can get from www.sourceforge.com\releases