MS Programmers --- Visual Source Safe ???

[bunker]

We have about 4 people doing Access programming here. None of us are "formally" trained in VB and have never used source safe but our boss wants us to start using it.

What are some of the advantages/disadvantages to using it?

I'm the type of guy that tries to avoid documentation and structure like the plague 😉, any info you have on it would be great!

Thanks in advance

 

[EagleKeeper]

SourceSafe is a version control system.

Check out the source files, modify them and return them for use.
If a file is checked out, others may view, but not check out for modifications.

If you are coding in VBA (MS Access) it may not help you much.
Most VBA code is embedded into the actual parent file. (Access, Excel, etc).
Therefore you will have only one file to control.

Other option would be to write the code seperately, have that under control, and a master user be responsible for integratinging into the database app.

Good luck

 

[Argo]

If a file is checked out, others may view, but not check out for modifications

Actually, if a file is checked out others may still check it out. You'll be just required to merge the changes (graphically) when you check the file back in. Also, sourcesafe isn't a dynamic code control system, meaning if others modify files you won't see the changes right away, until you explicitly tell source safe to update your view.

 

[joohang]

Yup. SourceSafe is kinda flaky. bunker, you and your colleagues might want to experiment it a bit to get used to it.

To avoid the trouble, only check out one file at a time and make sure to check back in when you are done.

 

[BuckleDownBen]

You defintely want to use some Version Control software. Sourcesafe probably isn't the best, but it's not bad and it comes with Visual Studio. The advantages are you can rollback changes made to your software. You can compare different versions of the same software to find where a bug was introduced. It prevents two people from working on the same code. It provides an easy means to back up all the code/files in one place (you don't have "production" code saved on local machines and no where else). It makes it easy to get the latest version of everything.

If there is more than one developer on a project, Source Code control is a must. It isn't as important if there is only one developer, but its still a good idea to have.

 

[bunker]

Right now our source control consists of an Excel spreadsheet that we enter what we're working on and a time when we started. We check to make sure no one else is working on it before touching it. Obviously not the best method, but it's worked for us so far.

I think the boss is just trying to piss us off by making us learn a new piece of software. 🙂

 

[joohang]

Originally posted by: bunker
Right now our source control consists of an Excel spreadsheet that we enter what we're working on and a time when we started. We check to make sure no one else is working on it before touching it. Obviously not the best method, but it's worked for us so far.

I think the boss is just trying to piss us off by making us learn a new piece of software. 🙂

I personally think that your boss is attempting to implement some good working practices. 😉

 

[manly]

VSS is almost universally considered a POS.

I've used Perforce before, and it's pretty good. You can try it out unrestricted for free (up to 3 clients). All programmers should use an SCM, even if they're working alone, except on trivial projects.

 

[Argo]

We're using Clearcase here. It's pretty cool especially when it comes to merges and branching. The only gripe I have with it is that it's so hard to do certain things.

 

[BuckleDownBen]

Originally posted by: manly
VSS is almost universally considered a POS.

I've used Perforce before, and it's pretty good. You can try it out unrestricted for free (up to 3 clients). All programmers should use an SCM, even if they're working alone, except on trivial projects.

I used VSS at my previous job. It is definitely not a POS. Its shortcomings are that it doesn't work well with a large number of developers. It doesn't work great if you have developers accessing it over the internet. We never tried having two coders work on the same file and merging the changes, so it may not do that well. For the situation the poster described it is perfect, especially since they most likely already own it.

Bunker-
Take the time to learn VSS. It will only take you about an hour. You will be happy you did. The first time you roll back some changes that put bugs in your code you won't be able to believe you coded without Source Control.

 

[CodeJockey]

We use VSS for all our projects, and it works very well. If you have developers working from remote locations, get SourceOffsite, which improves the performance over a slow Internet connection.

One other major feature (PVCS and probably all other Source Control packages also have it) is the ability to label the code at a particular point in time (for example, when you do a build and give it to the customer). You can then retrieve all files based upon the label (so you don't get changes that were made after that time). This lets you fix small bugs in the released code without dragging in code for partially completed new features.

VSS is probably the best to use if you are using Visual Studio. If you do your development with something else, then any Source Control package will definitely be an improvement over the makeshift spreadsheet system you currently use.