Versioning Toolbox: Effective Use Videos
| Introduction to the Versioning Toolbox | |
 |
Setting Up the Versioning Toolbox How to setup the Versioning Toolbox to work with your version control system. There are currently four supported source control systems; CVS, SVN, Team System (2005 and 2008) and Source Safe. |
|
Accessing the Versioning Toolbox's Functionality Covers the different ways to access the functionality of the Versioning Toolbox. |
| File History | |
|
Determining Changes Between Versions When looking at the version history of a file, the only available information about exactly what changed between versions is the check in comment. However, you'll often want to know specifically what code has changed. This video shows how to see all of the code changes that were made for any version in a file's history. |
|
Determining Changes Before Check In It's a good practice to review what changes you've made to a file before you check it into source control. This video shows how to see the differences between a file you are about to check in and the latest version of that file in source control. |
| Find Version | |
|
Using Find Version to See Developer Activity There are several times when you will want to determine what a developer, or set of developers, have worked on. For instance, when a developer is being code reviewed, you need to be able to tell which files that developer has worked on recently. This video shows how to see all of the checkins for one or more developers over a period of time. |
|
Using Find Version to Track Bugs This video shows how to determine the set of check ins that fixed a particular bug in your bug tracking system. |
| DIFFzilla | |
|
Launch Options Shows many of the different ways to run DIFFzilla from the features available in the versioning toolbox. |
| Version Graphics | |
|
Find Code Churn with Version Graphs Code churn is a measure of how much change is occurring in a code file. High churn often indicates less stable code. This video show you how to use the Version Grpahs to quickly identify periods of high code churn. |
| Version Visualizations | |
|
Date Schemes in Version Visualizations Shows you how to use the date based visualizations to answer questions such as, "How old is this code?", "What code has been written in the last two weeks?" and "What code was written during the last development cycle?" |
|
User Schemes in Version Visualizations This video shows you how to use the user based visualizations to answer "Who wrote this?" for any line of code in a source controlled file. |
|
Using Visualizations to Highlight the Most Recent Code A good metric for determining the reliability of a section of code is its age. This video shows you how to determine the relative age of each line of code in any file. |
|
Using Visualizations to Highlight High Risk Developers Everyone, at one point or another, has worked with another developer that they considered a high risk. Maybe that developer had a history of writing buggy code. Perhaps it's a junior developer. It could also be an experienced programmer who is new on a project and is unfamiliar with a code base. This video shows how to use the version visualizations to quickly identify code wriiten by one or more high risk developers. |
|
Using Visualizations to Highlight Developer Groups When there are large numbers of developers working on a code base, it's helpful to be able to see which development groups have worked on the different parts of code you're editing. This video shows how to use the version visualizations to quickly identify which coding groups have wriiten which sections of any code file. |
|
Using Visualizations to Highlight Current Release Code When you work on a file, it's very helpful to see what code has been written as part of the current release cycle. This video shows how to use the version visualizations to quickly identify which sections of any file have been written during the current development cycle. |
|
Using Visualizations to Highlight the Last Two Weeks of Code The age of a section of code can help determine the stability of that code. Newer code is going to be less stable than older code simply because it hasn't been through as many test or integration cycles. Because of this, it's very helpful to know what code has been written in the last two weeks, or any period of time. This video shows how to use the version visualizations to quickly identify which sections of any file were written during the last two weeks. |
|
Using Visualizations to Know Who to Ask for Help Trying to understand the new code can be extremely challenging. However, it's very helpful to know who wrote what parts of the code, so that you can ask that person for help if you need to. This video shows how to use the version visualizations to quickly identify who wrote any section of the code that you need help with. |
|
Version Visualizations in a Tool Window This video shows you how to view all of the version visualizations in a separate dialog. |