Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Best Practices with .NET and Visual SourceSafe 6
Message
From
11/12/2006 16:51:11
Mike Cole
Yellow Lab Technologies
Stanley, Iowa, United States
 
 
To
All
General information
Forum:
ASP.NET
Category:
Other
Title:
Best Practices with .NET and Visual SourceSafe 6
Environment versions
Environment:
VB.NET 1.1
Miscellaneous
Thread ID:
01176688
Message ID:
01176688
Views:
57
I 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!
Very fitting: http://xkcd.com/386/
Next
Reply
Map
View

Click here to load this message in the networking platform