Well you've certainly bailed a few companies out of a SourceSafe jam over the years, Ted. Some without even knowing it. My E-copy of your VSS book is almost worn out. :)
I dont see us moving out of the Micro$oft world here. Our VFP apps will be mostly gone by the end of the year, but have to be updated to use SQL tables until they are re-written and enhanced using .Net. That's the way they want to go and it is there call; I'm not a manager here, nor do I play one on PC. ;) We have MSDN here, but I don't know what level. The big reason we got it was to set up a test environment for SQL server. I asked if I could install Visio and was turned down, still haven't figured out why... I wasn't involved in the setup of SVN at Premier so I dont know all the details, but I know apache was involved somehow. I need to dig into it now that I am somewhere else, and hopefully management will follow my lead. But I don't want to lock myself into SVN based on my limited knowledge of it. I'm getting lots of good suggestions from those using something else and that is what I was hoping for. :) Lou -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Ted Roche Sent: Friday, February 04, 2011 11:17 AM To: [email protected] Subject: Re: VFP and Source control On Fri, Feb 4, 2011 at 11:24 AM, Lou Syracuse <[email protected]> wrote: > Is anyone using source control with VFP? Only the professionals. By definition, I think. You ain't one without the other, imnsho. > We need a solution that handles VFP and .NET projects. Documents and SQL > Server code would be good too. In my last company we used Subversion and > with Tortoise as the front-end and it worked pretty well; however Subversion > is Apache-based and I know nothing about Apache. Apache and Subversion are two completely different and unrelated projects. Subversion does not depend on Apache. You might have run a web-based application on Apache that let you access subversion over the web (does WebDAV sound familiar?) but the two are as separate as VFP and IIS. > I've had too many issues with VSS to consider it (plus I think it has been discontinued). Agreed. I continue to support existing installations, but don't encourage its use. If you ever think you're going to step outside the Microsoft cone of silence, I strongly recommend staying away from their proprietary solutions. But you'd probably expect that from me :) Open Source will set you free, and all that. If you're ever going to need access to the source code when you're not connected to the office network (on your laptop, in a plane, when the server's down, bringing in a remote consultant/employee, etc.), I strongly recommend you look at a "distributed version control system." They're a little more hassle to set up and a bit of a learning curve at first, but it means that remote code development and local code development can proceed unhindered by the source code control system. Most of the popular ones are very similar in functionality and capabilities, and it's worth doing a little shopping for the one that works best with your requirements: take a look at git, bzr ("bazaar"), or mercurial. The problem with asking for recommendations, of course, is that everyone can only speak from their own experience, and their own environments. We all have opinions on the "best" remote access software or the "best" printer. I'd encourage you to do a little research at http://en.wikipedia.org/wiki/Revision_control and see what best fits your needs. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com [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/023801cbc4a2$dab28630$90179290$@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.
