This is an overview of some of the changes you will encounter when going from SourceSafe to Subversion. Subversion is modeled on CVS, whereas SourceSafe is modeled on…. well… nothing (just a joke). In SourceSafe, you work in a shared code base or line (known as a “Project” in SourceSafe) which you “share” into [...]
This article will tell you how to get a build process. It uses CruiseControl.NET to automate the build. You can use any other tool you like including a .BAT file, but CruiseControl will do just fine. It’s very easy to set up, it uses an XML configuration file and does most of the difficult job like connecting to your source control, applying labels, and getting your files to build for you.
How to recursively branch your files in SourceSafe.
A summary of how to use Visual Source Safe (VSS) Pinning. Pinning is a feature that can be used to set a certain version as releasable, and when you run ‘Get latest version’ it will give you the pinned version, rather than the latest one, which may not be suitable for release yet. It also can be used in conjunction with Visual Source safe branching and sharing.
If you’ve ever had two or more source-safe projects with shared files, you might be shocked to learn that Visual SourceSafe 2005 breaks one of the holy grails of good design: user expectations. But alas, Visual SouceSafe 2005 merges changes, not branches!
If you’ve ever had two or more source-safe projects with shared files, you might be shocked to learn that Visual SourceSafe 2005 breaks one of the holy grails of good design: user expectations.
You would expect that, if you delete a shared file from one project, it gets branched. I mean, you deleted it, right? But alas, Visual SouceSafe 2005 shares deleted files!
Using Visual SourceSafe, we can put some text at the top of our source file and it will automatically be updated by SourceSafe when you check in the file. See below for an example. // Last updated by: // $Author: Sameera $ // $Date: 4/13/07 11:16a $ This will allow you to quickly see who [...]