Hi Mindy, PMFJI

But yes you can do all of what you asked.

In VSS you set the working forlder ro each user. You can have the copies locally or on a central server. It is probably best to have it locally this way the user isn't tying up the server.

To have a current version the developers check items in and out like your version. Once all complete items are checked in then you label it.

You can set VSS so only single check outs happen.

Once you label it, you can get a latest version to another directory by label. So if you do a label every night then you can have a current version the next day.

If you are looking into VSS i suggest you by a book on VSS.
Such as UT's Ted Roche - http://www.hentzenwerke.com/catalog/essvss.htm






>Hi Mike,
>Didn't take long for a question to arise!
>
>Here is my run-down of how we operate......currently our programs are all written in fox pro and we are using our own custom-written version conotrol. We are migrating to .NET, windows & web (many more windows forms though), and we are looking for a version control to be similiar to what we have.
>
>We have a large directory called "DEV" out on our network for all 7 or 8 developers to access. This is where all our programs, forms, and reports reside for developement, support, and testing. We also have all our programs, forms, and reports sitting in another large directory on the network called, "Current". This is where the current, live version of everything resides. We do not pull files from "Current".
>
>When a developer needs to make a program/form/report change, they check the program out in our version control which then doesn't allow anyone else to check that program out. The developer actually works on the copy that sits in "DEV" on the network and the testers test the changes from "DEV" as well. Once testing is complete, a checkbox in our version control is marked as "Check In". Everyday, we have an administrator who runs a build in version control. This takes the program changes in "DEV" that are marked as "Check In" and copies them over to "Current".
>
>Now, after all that...my question is this: Can we use Visual Source Safe as we use our current version control? I've read that a checked out VSS file goes into a working folder on your local PC? Or is that only true for web forms? Can we have working folders for each developer at the network level? Can we keep a development copy of all our files on the network in one directory as well as keeping the live copy of everything in another directory on the network?
>
>If you have any questions from me or if I've confused you too much, please let me know. You're welcome to e-mail me personally at melinda.shingara@csiu.org if that works better for you. I really appreciate your help!!
>
>Thanks,
>Mindy