We are using TFS for quite some years and it has been a very positive experience. I like the integrated tasks and add-ons for Outlook that convert issue related emails into work tasks, and the check-in process is integrated with the linking of tasks that are resolved or associated. I cannot imagine a life without source control anymore.

To make it work with VFP we had to restructure our VFP applications to use many smaller libraries that are all separated depending on their responsibilities. We did not try to do any code merging, we separated the code so much that no merging would be necessary in the first place. So no monster libraries or monster classes anymore, but everything neatly categorized and separated. We encourage developers to work only on one task and to divide the work into steps that are easy to finalize during a few hours, so we don't have files checked out for long periods of time.

The only disadvantage so far we have because using TFS and because it's not integrated in the VFP IDE, we have to manually add any new files. There are now some settings in the newer versions of TFS where that would also be done automatic, but in the end I prefer to have total control on the files that get checked out or added to source control.



>[I'm using Google Translate]
>
>I find the sad reality that VFP developers do not know or do not use source control. At least most people I know do not use it in their daily lives as if is "technology out of reach" or can not be used with FoxPro or would be very difficult or even unnecessary or tedious.
>
>This thread is to ask who of you use source control tools with FoxPro code, what tools you use, or if you know what tools are available, and share information about it.
>
>I think the responses, or lack thereof, you can get a better idea about this lack crawling on FoxPro. It will be something interesting at least.
>
>
>To begin with, I tell a little of my experience with this topic:
>
>Like many of you, I use FoxPro from the beginning, I made contact with source control in the late 90's with SourceSafe 6 (VFP 6, included in VS 6), and until last year (2013) it was used in all team developments I've participated, including personal mine.
>
>Since late last year at my workplace have made a technological renovation in which have unified all source control tools in use (svn, cvs, vss, etc) for various languages (Java, web development, Oracle, Cobol, etc) into a more modern source control tool (PlasticSCM) for which I have developed an Open Source (FoxBin2Prg) component to use with Visual FoxPro 9, that can be used indepently.
>
>Since April this year (2014) we can use source control in FoxPro 9 in the same manner as used in other languages ​​like Java or other for many years, but recently it is now possible because the development team (10 members about) can work even on the same components (forms, classes, etc) and mix changes visually, without having to edit them using the FoxPro IDE to copy/past methods manually.
>
>I am interested to hear your experiences.
>
>Regards,
>
>Fernando D. Bozzo
>
>PD: I may ask this in other forums to have a broader idea.