Fall 2007

A set of video tutorials from Dr. Wong appear here: http://www.bandgap.cs.rice.edu/sites/comp410resources/Team%20Explorer%20Tutorials/Forms/AllItems.aspx

The download you need for Visual Studio is here:
http://www.exciton.cs.rice.edu/iso/TFS/

I haven't quite found the way to prevent files from being checked in if they don't compile, but I have found the way to make sure they follow proper formatting/performance/design/etc and provide either warnings or errors on problematic pieces. Also, I have found the way to connect files to a testing system that will make sure a file pasts tests before being allowed onto the server. All of these (and probably the last one, although I haven't found it yet) appear under the "Team Project Settings/Source Control" when one right clicks on Team Project in the Team Explorer.

Please update this post to make it clearer or add information as you find new things.

Derek, Hubert and I (Dave) just tested the source control - rather easy and intuitive. There's probably no way to limit code if it doesn't compile, but we got branching and merging to work so that should really help to eliminate that problem. Also, Derek, you need to stop doing work and start playing video games - good (and a lot of) work done there.

 

Compile tests for source control acceptance was dropped as a feature from the RTM version of TFS.  It can be done however, but it is a royal pain involving command line scripts.   Info on unit testing and TFS can be found in the Comp410 Resources site: http://www.bandgap.cs.rice.edu/sites/comp410resources/Lists/C%20and%20VSNET%20Resources/AllItems.aspx

-- SW