Viewers: in countries Watching now:
This course is a gateway to learning software version control (SVC), process management, and collaboration techniques. Author Michael Lehman reviews the history of version control and demonstrates the fundamental concepts: check-in/checkout, forking, merging, commits, and distribution. The choice of an SVC system is critical to effectively managing and versioning the assets in a software development project (from source code, images, and compiled binaries to installation packages), so the course also surveys the solutions available. Michael examines Git, Perforce, Subversion, Mercurial, and Microsoft Team Foundation Server (TFS) in particular, describing the appropriate use, features, benefits, and optimal group size for each one.
Tagging in TFS is called creating labels, and it's really easy. You do it from the Source Code Control Explorer. Remember, tagging is the process of identifying a particular set of changes in your repository with a label so that you can come back later and check that out, such as when you shipped Version 1, and you start working on Version 2, if you need to roll back to the Version 1 changes so that you can make a bug fix and then come back. So we'll go to this TFSSample-- that's the name of our project folder-- we'll go down to Advanced and say Apply Label.
And so for our Label, we're going to say v1 and for our Comment we're going to say This is version 1. Now, you can apply this label to anywhere you want. You can say the Latest Version, the version that's in your Workspace, a particular Changeset or a Date or even to another Label. In this case, we're going to just pick Latest Version and click Create. And now we see that everything is all set, it is Label v1 that's been created, and here you see a log of all the other things that we did before, replacing the file with different versions and creating the label.
So once again, now if we come here and say View History, you can see that not only is there is a Changesets tab, there is a Labels tab, and this allows you to keep track of the labels separately from the Changesets. So now I can do something like come here and say Get This Version. Now, in this case, it says all files are up to date, we didn't actually do anything. But if we had gone back to f1.cs and started to make another change and say we said Node not found and we saved it and we checked it in, now if we come back to our History and go to the Labels, we can right-click here and say Get This Version. We come back to look at f1.cs, it's got Website.
But if we come back to the Changesets and Refresh this, and come back and say Get This Version, we can now see that it's back to Node. And that's basically all it is to use labels in TFS, it's all integrated into Visual Studio, and it's all done by using this Labels tab inside the History window.
There are currently no FAQs about Fundamentals of Software Version Control.
Access exercise files from a button right under the course name.
Search within course videos and transcripts, and jump right to the results.
Remove icons showing you already watched videos if you want to start over.
Make the video wide, narrow, full-screen, or pop the player out of the page into its own window.
Click on text in the transcript to jump to that spot in the video. As the video plays, the relevant spot in the transcript will be highlighted.