I have some experience with it and it works ok. If there is a conflict VSS will notify you and ask you to resolve it. Note that the checkbox enables multiple checkouts per VSS database so if you are working in a large, company-wide VSS database all projects in that database will have multiple checkouts enabled! We had this issue and decided simply to create a separate VSS database to host newer projects that wanted this feature enabled.
HTH, Dadi. -----Original Message----- From: Bayley, Alistair [mailto:[EMAIL PROTECTED] Sent: 2. desember 2004 09:23 To: '[EMAIL PROTECTED]' Cc: 'xperroni' Subject: RE: [XP] Code management practices Apparently it does, although I have no eperience with it (but I will have soon, as we're about to start using multiple checkouts). You must run the VSS Admin tool, Menu -> Tools -> Options... -> General tab -> check "Allow multiple checkouts" It's not clear from reading the Help what happens when you have a check-in conflict; I'd hope that something similar to the "Resolve Merge Conflict" process would be triggered. > -----Original Message----- > From: Ron Jeffries [mailto:[EMAIL PROTECTED] > Sent: 01 December 2004 20:35 > To: [EMAIL PROTECTED] > Subject: Re: [XP] Code management practices > > > On Wednesday, December 1, 2004, at 3:13:57 PM, xperroni wrote: > > > The approach advogated by XP -- let everyone write to files > and then > > solve conflicts at code releasing time -- seemed a good > solution. In > > eXtreme Programming Installed there is a very interesting > description > > of a code management policy, but it is admitedly a simplified > > explanation. What references (specific or not) you recommend on the > > subject of code management? Are there any commentaries or personal > > experience you'd want to share? > > Does Source Safe allow two or more people to check out a > file, and then > issue a notice when the second person saves it back? Or does > it not have > that ability? > > Ron Jeffries > www.XProgramming.com > If we're not shipping our software when it's ready, > it's poor business practice. > If we're not sure whether our software is ready, > it's poor software practice. ----------------------------------------- ***************************************************************** Confidentiality Note: The information contained in this message, and any attachments, may contain confidential and/or privileged material. It is intended solely for the person(s) or entity to which it is addressed. Any review, retransmission, dissemination, or taking of any action in reliance upon this information by persons or entities other than the intended recipient(s) is prohibited. If you received this in error, please contact the sender and delete the material from any computer. ***************************************************************** To Post a message, send it to: [EMAIL PROTECTED] To Unsubscribe, send a blank message to: [EMAIL PROTECTED] ad-free courtesy of objectmentor.com Yahoo! Groups Links [Non-text portions of this message have been removed] To Post a message, send it to: [EMAIL PROTECTED] To Unsubscribe, send a blank message to: [EMAIL PROTECTED] ad-free courtesy of objectmentor.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/extremeprogramming/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
