visualsourcesafe

How to use the sourcesafe in a multiuser environment.i am not worried abt the forms(checkin & checkout)-i want info abt the project..can each user check in and check out the project or MAKing writable enough....
Advance thnx
sridhar12345Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

sridhar12345Author Commented:
msdn abt sourcesafe dint help
0
HarmnKardnCommented:
Multiple users can check out a project simulatenously, but not all files within the project.  SourceSafe does not let multiple users modify the same file in realtime (that is, show the other developers edits while you're editing the same file).  I have never actually seen an IDE/version control system that supports this.

With SourceSafe, users should not both simultaneously check out the same file, unless they wish to deal with merging the changes from the two seperate files at another time.

Of course, SourceSafe lets two users check out different files in the same project, and work on them as necessary.
0
dmstratCommented:
I would add to HarmnKardn notes by saying that making writable should be enough for the .vbp file for the duration of the modification of the code as long as you aren't adding new files to the project.  In that case you need to check out the main .vbp/.vbg file so that it can be properly modified to include the new files being created.  Other than that, your "get latest version" should be enough to keep up with the latest "happy" code while the main .vbp file isn't being corrupted by your specific development environment file locations.  

I would also suggest you try it out yourself with two computers that have different "working directories" to show how keeping a "writable" version of the .vbp/.vbg file will be enough for regular work.  Then, when it comes to compiling the project, you can use a single computer that checks out all the files, compiles, and checks in.  

Don't forget to "label" each milestone compile directly in VSS. It's not required, but a good technique.

Dan M.
dmstrat@yahoo.com

0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

sridhar12345Author Commented:
thnx for the comments...yeah we hav to check out the project for addin a form..
The doubt now is will the administrator be working on the main copy or is it possible to hav a seperate workin directory for him
0
HarmnKardnCommented:
There is no "main" copy...ever user working on the project has a copy of the whole project on their own local disk.  For each user, changes to files not checked out are prohibited, changes to files that are checked out are saved locally and to the server.  All users have seperate working directories on their own machines.
0
dmstratCommented:
Continuing with HarmnKardn's notes: the files on the server are not changed until the files are "checked in..."  Therefore, once you establish a "publish" routine where your developers all check in their changes, the project should compile with all the changes made at that time.  You then put a "label" on the project to signify your milestone event after you confirm the compile is what you want.  This compile can be done on any machine that has access to the VSS database and doesn't have to be done on the server.  

Now you should have your complete project in place, compiled, and ready for the next set of requirements.  The person who did the build can continue with their work and developers can check-out the files they need to continue working.

It's not a "requirement" to check-in all the files before the "official compile" but it's a good idea to let the developers know that it's time to turn their current stuff in so that the compile is up to date.  

Dan M.
dmstrat@yahoo.com
0
sridhar12345Author Commented:
"No main copy" ??? we will be prompted whether v wan to replace the files (in our working directory) from the main directory...
so i think there will b a master folder which consists of the latest changes (performed by all users)...my question is -is that folder the same folder of the admininstator's working folder
0
HarmnKardnCommented:
The "master" copies of the files are stored in the VSS database on the VSS server.  It is not simply a folder on a hard drive somewhere that has a copy of all the files in your project.  

So this "master folder" is *not* the administrators working folder.
0
dmstratCommented:
If you want to think in the way of a "master folder", everyone has the same copy of the files when each user uses the "get latest version" action when all of the files that the user requesting the action is "checked-in".  The use of "get latest version" means that the user will receive the current version of all the files at the time that they were last checked-in.  Therefore, if developer 1 has two files checked out and has done some work on the file(s) and developer 2 does a "get latest version" that includes those two files.  Then developer 2 will receive a version of those files BEFORE those files were checked out.  Meaning that those two files will not have the changes that developer 1 is currently performing on those files.  

However, once developer 1 "checks-in" those files, then developer 2 can "get latest version" and receive those changed files for their local copy.  

Even with all the checking in and out, an administrator (or just developer 1 or 2) could "get latest version" on their local machine, do a compile, and that version will be the most up to date version of the application you are working on minus any changes currently being done by "checked-out" files which may not have "working code".  That was the reason for "notifying" the developers to check in their good code before the "compile" time.

However, you can "view" a virtual master folder when you open the VSS application.  That application accesses the VSS Database and creates what may appear to be the "master folder" you are talking about.  However, you will not find it on any machine's directories.  If you do happen to find a matching directory structure on the server, it is strickly a "working folder" that's it, nothing more.  So, don't worry about "master folders" as each "working directory" can be a copy.
0
CleanupPingCommented:
sridhar12345:
This old question needs to be finalized -- accept an answer, split points, or get a refund.  For information on your options, please click here-> http:/help/closing.jsp#1 
Experts: Post your closing recommendations!  Who deserves points here?
0
DanRollinsCommented:
sridhar12345, an EE Moderator will handle this for you.
Moderator, my recommended disposition is:

    Save as PAQ -- No Refund.

DanRollins -- EE database cleanup volunteer
0
Computer101Commented:
PAQed - no points refunded (of 100)

Computer101
E-E Admin
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.