Yes, we are storing both, binary and text, like SourceSafe did in the past.
This is for many reasons:
1) because regenerating binaries have a cost in time, not important in few files, but with +1600 files it does
2) because velocity: we need to change between branches and execute the code of that branch directly
3) because backup reasons: people do mistakes, and sometimes forget to generate the text version (even having a menu for doing that) then sometimes files are not in sync. But these situations are detected early, and the quick fix is to generate the binary and add the text part in the next changeset. Only problem is thar previous changeset can not be cherry picked.
We do not use the VFP project integration, because we do not use mssccc api and files are never readonly, which means nobody can block nobody, like un sourcesafe, which is something wanted because blockings are not good for anyone.
With sourcesafe we have got many projects blocked by people that went to vacation or changed job, not allowing to continue working in the same project because many files where checked out and never checked in.
I explain some of these questions in the VFPx help part of FoxBin2Prg, describing one way of working flow with PlasticSCM, which can be applied to other SCMs. El 17/6/2016 4:31, mbsoftwaresolutions@mbsoftwaresolutions.com escribió:
On 2016-06-16 13:26, Fernando D. Bozzo wrote:
Well, I think that you can see it by yourself. Downloading and making a quick test is faster than the time required to write an email.
We have 2 independent/distributed teams working with VFP 9 projects with more than 1.5 millon lines of code between forms, classlibs, menus and prgs on a DVCS system (PlasticSCM) sharing, branching and merging code since mid 2014, and I can say that FoxBin2Prg was the only tool that not only allow merging, but do it showing PRG-style code to the Developer, which is what we know better. No XML (excect in table data and reports), no "rare" text.
Forms, Classlibs and Menus are converted to PRG-style, and in 2+ years we didn't have any problems when merging and regenerating operative binaries.
I think that having at least 2 VFPx projects oriented to git ("bin2text" from Lutz Sheffler and "git utils" from Mike Potjer) and even FoxUnit using it as the bin*text conversor gives some confidence about it.
But, again, the only way to know if it's for you is doing a test with a copy of your files.
Fernando,
So in your DVCS (PlasticSCM), you're not storing the binary ??X/??T files, but you are instead storing the results PRG-like equivalents of them? Do you create those via ProjectHook calls or how/when do you do the conversions? Or, perhaps you're storing the binary files AS WELL AS THE PRG EQUIVALENTS???
Very interesting.
[excessive quoting removed by server]