Check out branching and merging in VSS.



> am wondering if anybody had any good info about best practices when using VS.NET with VSS. How are multiple versions of the same project handled (IE, production vs. development code)? How are projects structured to make the most out of SourceSafe's features?
>
>The specific problem we are having is when we have a bug in the production version of code while the code is in development. It's difficult to do a "quick fix". Right now we are copying our entire database and archiving it everytime we put out a production version of code, and when we need to access that it's a bit of work to reconnect to the archived SourceSafe version, load the project, and then merge the changes with the in development version.
>
>Thanks for any advice!