Using v4.1.4 and plan on moving from "Check Out/Edit/Check In" to "Get/Edit/Merge". Other than changing the settings within the vault client and integrated client within Visual Studio, what other steps do we need to take to get this switched over?
Do we want/need to unselect the "Require exclusive locks" setting on the repository?
Will we need to remove the Read-Only attribute on all of our existing local (work) files? Will a get latest remove that for us?
What will happen if some uses don't make the switch and continue to work in "Check Out/Edit/Check In"? (Not all uses follow directions.)
Any thing else we should look out for?
Thanks,
Andy Robinson
PeaceHealth
Moving from Check Out/Edit/Check In -> Get/Edit/Merge
Moderator: SourceGear
Re: Moving from Check Out/Edit/Check In -> Get/Edit/Merge
Probably a good idea, because a user who decides to use VSS mode would end up automatically checking their files exclusively, and that would prevent other users from checking in their files.Do we want/need to unselect the "Require exclusive locks" setting on the repository?
A Get Latest with Overwrite will reset the read-only bit to writeable. Be sure you checkin/backup any modified files in your working folders. You can also just choose to Edit a file, which will make it writeabe.Will we need to remove the Read-Only attribute on all of our existing local (work) files? Will a get latest remove that for us?
It mostly won't affect other users, unless a VSS mode user checks out a file exclusively -- CVS mode users will still be able to edit files in their working directories, but won't be able to check in any files exclusively locked by another user.What will happen if some uses don't make the switch and continue to work in "Check Out/Edit/Check In"? (Not all uses follow directions.)
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager