Actually Paul, I am with you on the IDE integration. Especially in VFP where it is basically a hack no matter how you are doing it. Some solutions are better than others, but basically VFP wasn't designed to integrate with source control. Being able to compare code is great, but for the VFP side it isn't necessary for us. We are phasing out VFP which will take a while, and only the part-time programmer and I will be using it (and I do most of my work in .Net). Our next programmer will be a .Net guru with little or likely no VFP experience.
We're a small shop, but we've learned (hopefully) that you can't say "put your source code here.. and here... and keep a copy (or two, or three...) on your local machine" and still expect to have multiple developers working on things. That's the main reason I want source control - the code goes <<HERE>>, end of statement. Lou -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Paul McNett Sent: Friday, February 04, 2011 10:41 AM To: [email protected] Subject: Re: VFP and Source control I personally think integrated source control is a mistake, and not just for VFP. The process of developing should be completely separate from the process of merging, diffing, updating, and committing to/from a source control repository. Then again, I don't use an IDE at all anymore, so just feel free to ignore me I guess! Paul [excessive quoting removed by server] _______________________________________________ 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/023701cbc4a0$d7c0f670$8742e350$@com ** 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.
