visual source safe

Printable View

Dec 12th, 2002, 02:58 PM
JimMuglia

visual source safe

Hey guys,

To put it bluntly, I'm full of hooey when it comes to VSS. My boss always tells me to save stuff in Source Safe, which I do; but I have no idea what I'm doing or why.

What the heck is source safe? what does it do? How am I better off using it? Please don't send me any links, unless its exrtremely straightforward and for guys without a hint of what VSS is for.

Does it backup the code if I lose my drive. somebody please make this VSS thing plain and clear to me once and for all, without making me read an Encyclopedia.

Jim
Dec 12th, 2002, 03:07 PM
Cander

It is a 'SAFE' for our code and all its versions. If you make a horrible mistake and cant figure out what is wrong, you can compare your current code to a previous version and even go back to a previous version if need be.

also it makes it easier for mutliple developer projects by keeping developer A from making changes to Class A while developer B is working on it.
Dec 12th, 2002, 03:21 PM
JimMuglia

Quote:

Originally posted by Cander
It is a 'SAFE' for our code and all its versions. If you make a horrible mistake and cant figure out what is wrong, you can compare your current code to a previous version and even go back to a previous version if need be.

also it makes it easier for mutliple developer projects by keeping developer A from making changes to Class A while developer B is working on it.

So everytime we save something to Source Safe, it creates a type of version number for that source code that distinguishes it from the source code (for the specific program) last saved to it?
Dec 12th, 2002, 03:30 PM
Cander

Quote:

Originally posted by JimMuglia
So everytime we save something to Source Safe, it creates a type of version number for that source code that distinguishes it from the source code (for the specific program) last saved to it?

Exactly. Except the proper term is 'Check it in'. When you are in the VB IDE with a Source Safe project open, you will see a lock icon in the Project Explorer and all its files. Just right click a class file, form file, etc and choose Check Out. When you are done with it, Right click again and choose Check In. If you want to discard any changes you made, or didnt make any changes to a checked out file, right click and choose Undo Check Out which will keep Source safe from creating a new 'version' in its database.
Dec 12th, 2002, 04:53 PM
techgnome

We use it to also help compile different versions for different clients. Cliant A may use version 100, but Client B may be only on version 74. So, when I need to get the build for Client B, I know which points get. (Assuming every thing has been properly labled.. pffffft!)
Dec 13th, 2002, 01:17 PM
JimMuglia

Quote:

Originally posted by Cander
Exactly. Except the proper term is 'Check it in'. When you are in the VB IDE with a Source Safe project open, you will see a lock icon in the Project Explorer and all its files. Just right click a class file, form file, etc and choose Check Out. When you are done with it, Right click again and choose Check In. If you want to discard any changes you made, or didnt make any changes to a checked out file, right click and choose Undo Check Out which will keep Source safe from creating a new 'version' in its database.

Thanks for all the clarification, folks. I apprecaite it.