The standard project version numbers have used a Dewey decimal notation consisting of numbers separated by periods. The format of a version number appears as major.minor.revision, where
> Major version numbers identify significant functional changes.
> Minor version numbers identify smaller extensions to functionality.
> Revision version numbers signify even finer grained changes such as bug fixes.
You can extend this scheme if you need to. Visual SourceSafe's archiving functionality allows you to retrieve any prior version of existing code. This can happen if changes are made to the code that create a serious problem in the functionality of the project. Using the archived versions, you can rollback to the version that did not have the changes.
Visual SourceSafe also allows you to create custom versions of the same application. This could happen if you needed two slightly different versions of a project. In our discussion of reusing the product component for the ASP page, we mentioned that it would be best to create a new application using some of the old code for the product component. In this case, we would want a copy of the original project to become a new project that we could modify according the specifications of the ASP project. Let us look at how Visual SourceSafe allows us to do versioning.
One approach for tracking versions or builds of projects or applications in Visual SourceSafe is to use labels. By placing a label on the parent project of a program, all of the child projects and files will inherit that label. Labels are simply descriptive strings that we can apply to any version of a project. A label is a free-form string which can contain up to 31 characters. The following are all examples of valid labels: "1.0", "2.01b", "Beta 3" and "Approved by Tester1". Visual SourceSafe tracks the history of the project, allowing us to label a project when we have reached a certain level of development (for example, version 3.05.234). Later on, we can refer back to the files in the project, as they existed at the time you labeled the project.
We can label a project by going into the SourceSafe Explorer, right mouse clicking on the project and selecting Label:
Was this article helpful?