Visual Source Safe 6c Versioning

[Chris Fink]

Our team is using VS.NET 2005 and Visual Source Safe 6c. We keep all of our
source code in Visual Source Safe and version our applications using the
assemblyinfo file. My question is this: Is there a way to version an app
using VSS and lock it down a specific version or check-in from any changes?
To elaborate, lets say the developer is finished doing development on v2 so
they check-in all their code to VSS and notify the lead to deploy v2 to the
test system. The developer then begins working on v2.1. I want to lock down
v2, keeping it as a stable release, and force all developers to only use v2.1
going forward. This lockdown concept allows our leads to go back to any
prior stable version, ensuring that the code is untouched and can be deployed
to our production systems in the event of a problem.

I am sure this is a fairly common requirement when working in a team
environment with frequent releases.

[Markus Stoeger]

Chris Fink wrote:

Our team is using VS.NET 2005 and Visual Source Safe 6c. We keep all of our
source code in Visual Source Safe and version our applications using the
assemblyinfo file. My question is this: Is there a way to version an app
using VSS and lock it down a specific version or check-in from any changes?
To elaborate, lets say the developer is finished doing development on v2 so
they check-in all their code to VSS and notify the lead to deploy v2 to the
test system. The developer then begins working on v2.1. I want to lock down
v2, keeping it as a stable release, and force all developers to only use v2.1
going forward. This lockdown concept allows our leads to go back to any
prior stable version, ensuring that the code is untouched and can be deployed
to our production systems in the event of a problem.

I am sure this is a fairly common requirement when working in a team
environment with frequent releases.

How about creating a v2.0 branch into some other directory? Everyone can
keep on working on the main branch, while the v2.0 branch stays
untouched. Additionally you can set a label on the branch, so you can
easily spot (and revert from) any unauthorized changes made to it.

You could even remove write access from the v2 branch using the source
safe admin tool.. but I think that's going to far. branch+label should
be enough.

hth,
Max