I'd recommend going ahead and downloading a recent copy of each to be installed using the guidance below.įor the purposes of this article I'm using: I've chosen them for no particular reason, though all are freely available, seem to be in growing use, and support current software versions. In fact, all three duplicate the majority of each other's SVN functions since all include "Subversion". There are many alternatives to these tools. TortoiseSVN - Windows Explorer context-menu based SVN utility.VisualSVN Server - SVN web server to handle requests across HTTP connections.Perhaps some source code you found online and have modified.
You already have personal code you work with using VS2008 and are storing it on your computer.( Where all your hard earned cash has been invested) You already have Visual Studio 2008 ( not Express) installed and running on your Vista machine.You are NOT independently wealthy ( you do not have the capitol to invest in enterprise development solutions).Getting Startedįor the purposes of this article, I'll assume the following: This article attempts to translate my lengthy research among this mire into a helpful article suited to those entering the year 2009. While there are many articles about how to set up and use a source code control system, I found many were limited, dated, or uncompleted or they dealt with a much larger team approach to coding. In this article I'll describe how to transition from simply saving your code in folders on your computer, to using a revision control system which should safeguard your code and allow code "tinkering" without destructive or irreversible consequences. Ultimately, this created too much extra work and sweat. Needless to say, I've lost work due to hardware failures, inadvertent deletion, and just plain "breaking" my working code. Though I've been programming computers as a hobby since 1980, most of this was done on single machines by myself.
0 kommentar(er)
