D'Arcy from Winnipeg
Solution Architecture, Business & Entrepreneurship, Microsoft, and Adoption

Dev Teach Day 3 - Source Control Best Practices with Bil Simser and James Kovacs

Wednesday, November 28, 2007 12:15 PM

Are there really places that just use zip files for source control? Wow. I've been lucky to never have worked anywhere like that...VSS was always the lowest point I was at.

Optimistic locking is a good thing; keeps things current.

Friends don't let friends use VSS.

Tortoise SVN has an adapter for TFS that allows you to see the status of your files (checked out, not checked out) in your explorer! Very kewl.

Branching - How to Structure Your Sourcecode Folder

Subversion can move the folder structure on your client machine much easier than TFS (which needs you to create a new workspace on the TFS server).

You have Trunk and Branches. Trunk is your main, Branches are short-term areas to work on pre-existing code.

So if you want to pull out a certain version, then you pull it out and stick it into the branch directory, but when you're done with the change (and label/tag it), then you delete the branch. This keeps things clean, and it doesn't keep extra versions of files around (because if you ever need to get that, then you just get that "label" of the code).

Simser just dissed his child! (or was it Vista the OS?)


There are tools available in TFS and Subversion that will enable merging of files.

Random Questions about Subversion and TFS

TFS uses SQL 2005, Subversion uses the file system or an embedded database product

TFS offers better security. You can implement greater security in Subversion, but it takes a bit more work.

W00t...good session!



No comments posted yet.

Post a comment