Michael J. Babcock, MCP wrote: > I have some source checked out that is for a somewhat long term project. > My colleague needs to check out a couple of those files due to some bug > fixes that will be delivered prior to my project being implemented. He's > leery of the MERGE feature in VSS. I personally have not used the MERGE > feature. > > For those who have: do you feel comfortable with it?
No, absolutely not. SourceSafe integration with VFP isn't trustworthy. This isn't entirely SourceSafe's fault: VFP doesn't lend itself very well to source control, given that most source is in the form of a pair of binary files (the dbf and the fpt). But... SourceSafe is pretty sucky at scaling beyond a single user on a single machine, too. It just wasn't really designed to scale. You won't be able to reliably merge your changes with the other developer's changes (unless scctext.prg has gotten *much better* at this since I last looked at it) because the tools don't know how to merge source changes from inside VFP's binary structure. I tried to overcome these limitations with my scX project, and came close, but I'm pretty sure merging the plain-text .sc files that scX manages would be unreliable, too. There's just too much inside VFP that gives meaning to proper ordering of records, ordering of properties and methods, etc. A simple merge wouldn't preserve those things... If you are interested in taking a look at scX, read this page first: http://paulmcnett.com/scX.php > I haven't bought TR's book yet > (http://www.hentzenwerke.com/catalog/essvsstoc.htm), but know I > should...nonetheless, your comments appreciated! > > Perhaps today is the day to buy his book! Yes, buy the book. Even though like a quarter of it is dedicated to listing the contents of scctext.prg because it is "an interesting read" (sorry Ted, couldn't resist <g>), it does a great job of explaining how SourceSafe and SourceSafe integration with VFP works. I don't have a ready answer for you, other than to mention that this is one of the areas where VFP is seriously deficient compared to other development environments, where source code is saved in plain-text files and thus amenable to working with external tools, including very important ones like source control systems. This message didn't help, did it? -- pkm ~ http://paulmcnett.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
