Source Versions?
-
Hello, I have recently developed a small/medium sized application. Due to some sloppy coding techniques ( :~ ) I didn't comment any of the code (it is a personal project). I am going through the code removing anything that I have commented out/enhancing code. I would like to be able to save different versions of my work; in case I delete a comment/piece of code I need, I'd like to have the functionality to go back to the specified version. I have looked into source control; however, it seems that I need to have a server set up to do so. Is it possible to set up different versions of my code without requiring a server to connect to? (Since it is only myself working on the project, it wouldn't make sense to put the code out remotely or on a different computer.) I am using Visual Studio .Net 2003. Any suggestions would be greatly appreciated! Thanks, Mitch My sig: "And it is a professional faux pas to pay someone else to destroy your computer when you are perfectly capable of destroying it yourself." - Roger Wright Get Perpendicular! (Hitachi Storage) My CodeProject Blog Most recent blog post: April 11
But the "Server" can run locally, can it not? (Yes it can, I'm working this way) The main idea of an standalone server is 1st level backup: when crashing your computer, you don't crash your history.
Pandoras Gift #44: Hope. The one that keeps you on suffering.
aber.. "Wie gesagt, der Scheiss is' Therapie"
boost your code || Fold With Us! || sighist | doxygen -
Hello, I have recently developed a small/medium sized application. Due to some sloppy coding techniques ( :~ ) I didn't comment any of the code (it is a personal project). I am going through the code removing anything that I have commented out/enhancing code. I would like to be able to save different versions of my work; in case I delete a comment/piece of code I need, I'd like to have the functionality to go back to the specified version. I have looked into source control; however, it seems that I need to have a server set up to do so. Is it possible to set up different versions of my code without requiring a server to connect to? (Since it is only myself working on the project, it wouldn't make sense to put the code out remotely or on a different computer.) I am using Visual Studio .Net 2003. Any suggestions would be greatly appreciated! Thanks, Mitch My sig: "And it is a professional faux pas to pay someone else to destroy your computer when you are perfectly capable of destroying it yourself." - Roger Wright Get Perpendicular! (Hitachi Storage) My CodeProject Blog Most recent blog post: April 11
I can tell you this. Restoring a DB with source safe can be effin painful!!!
-
I can tell you this. Restoring a DB with source safe can be effin painful!!!
painful as in slow-painful.
-
Hello, I think I will go with Tortoise CVS; it looks lite it is a free alternative to source safe. Thanks for the info... Thanks, Mitch My sig: "And it is a professional faux pas to pay someone else to destroy your computer when you are perfectly capable of destroying it yourself." - Roger Wright Get Perpendicular! (Hitachi Storage) My CodeProject Blog Most recent blog post: April 11
Mitch (Programmer2k4) wrote: I think I will go with Tortoise CVS At least look at Tortoise SVN (subversion) if you are considering tortoise CVS. Depending on what you do, and how you do it, CVS may be enough for you. Especially with only a single person in the directory tree. However, you should always examine your choices. Tortoise SVN has the same capability of integrating with windows explorer, but on a Subversion based storage. Choose one because it is best for you, not just because it is the first free one you find. Look at the others mentioned here and then make a choice. I won't malign any of the ones mentioned, not even CVS, but CVS is an older style of source control. Know what you are getting. At work we use both CVS and SourceSafe on the same sources, and to servers in different buildings. We use Subversion on a closed network where we have more freedom of choices (all visible network software has to be approved, and subversion is not on the approved list yet). Know what you are getting and why you want it. Perhaps even post why you chose what here, you might get a few pointers on improvements or other software that does that particular activity better, but it was harder to find. :) _________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
Hello, I have recently developed a small/medium sized application. Due to some sloppy coding techniques ( :~ ) I didn't comment any of the code (it is a personal project). I am going through the code removing anything that I have commented out/enhancing code. I would like to be able to save different versions of my work; in case I delete a comment/piece of code I need, I'd like to have the functionality to go back to the specified version. I have looked into source control; however, it seems that I need to have a server set up to do so. Is it possible to set up different versions of my code without requiring a server to connect to? (Since it is only myself working on the project, it wouldn't make sense to put the code out remotely or on a different computer.) I am using Visual Studio .Net 2003. Any suggestions would be greatly appreciated! Thanks, Mitch My sig: "And it is a professional faux pas to pay someone else to destroy your computer when you are perfectly capable of destroying it yourself." - Roger Wright Get Perpendicular! (Hitachi Storage) My CodeProject Blog Most recent blog post: April 11
I've been using Subversion for years for local projects. Outside of some annoyances with the repo browser, it works great. All you have to do is: Install Subversion Install TortoiseSVN (you can also install Ankh, which integrates within VS; I found it too slow for large projects) Tortoise integrates most commands directly within Windows Explorer, so a simple right-click will give you access to all the goodies. Backup consists of a simple command via command line. I wrote my own .vbs script that backups the repository and compresses it to a .rar file. The Tortoise help file is fantastic and should be all you need. See the heading "Local Repository Access" for creating your repository and then follow the "Daily Use Guide" for usage. For more in-depth info, there's an online book here: http://svnbook.red-bean.com/
:suss: Pssst. You see that little light on your monitor? That's actually a government installed spy camera. Smile and wave to big brother!
-
I've been using Subversion for years for local projects. Outside of some annoyances with the repo browser, it works great. All you have to do is: Install Subversion Install TortoiseSVN (you can also install Ankh, which integrates within VS; I found it too slow for large projects) Tortoise integrates most commands directly within Windows Explorer, so a simple right-click will give you access to all the goodies. Backup consists of a simple command via command line. I wrote my own .vbs script that backups the repository and compresses it to a .rar file. The Tortoise help file is fantastic and should be all you need. See the heading "Local Repository Access" for creating your repository and then follow the "Daily Use Guide" for usage. For more in-depth info, there's an online book here: http://svnbook.red-bean.com/
:suss: Pssst. You see that little light on your monitor? That's actually a government installed spy camera. Smile and wave to big brother!
I was going to suggest something similar for CVS but Subversion does seem a better choice. Elaine :rose: The tigress is here :-D
-
I've been using Subversion for years for local projects. Outside of some annoyances with the repo browser, it works great. All you have to do is: Install Subversion Install TortoiseSVN (you can also install Ankh, which integrates within VS; I found it too slow for large projects) Tortoise integrates most commands directly within Windows Explorer, so a simple right-click will give you access to all the goodies. Backup consists of a simple command via command line. I wrote my own .vbs script that backups the repository and compresses it to a .rar file. The Tortoise help file is fantastic and should be all you need. See the heading "Local Repository Access" for creating your repository and then follow the "Daily Use Guide" for usage. For more in-depth info, there's an online book here: http://svnbook.red-bean.com/
:suss: Pssst. You see that little light on your monitor? That's actually a government installed spy camera. Smile and wave to big brother!
Is it really important to install Subversion first ? I did it.. but i didn't really needed it (altough if I'd use backup and other commands not handled by Tortoise SVN)
All the label says is that this stuff contains chemicals "... known to the State of California to cause cancer in rats and low-income test subjects."
-
Christian Graus wrote: Sourcesafe certainly does not, and I'm sure Subversion doesn't either. I'll look into Source Safe. Thanks for the suggestion. Christian Graus wrote: Wrong also - you should always keep your code base on at least 2 machines, preferably in different buildings. Unless you do a daily backup ? I usually back up projects once a month, or after I make a large change. Thanks, Mitch My sig: "And it is a professional faux pas to pay someone else to destroy your computer when you are perfectly capable of destroying it yourself." - Roger Wright Get Perpendicular! (Hitachi Storage) My CodeProject Blog Most recent blog post: April 11
Mitch (Programmer2k4) wrote: I usually back up projects once a month Dude! Whether you are or aren't using SVN or some other source control, just right a ZIP batch script that will ZIP all your work and dump it onto a datetime stamped folder onto the server somewhere. Daily backups are essential. It's also a good selling point with some clients! Nothing like a client paying you to redo work you shouldn't have lossed in the first place. Cheers, Simon sig ::
"Don't try to be like Jackie. There is only one Jackie.... Study computers instead.", Jackie Chan on career choices.
article :: animation mechanics in SVG blog:: brokenkeyboards
"Most of us are programmers, but a few use VB", Christian Graus -
I can tell you this. Restoring a DB with source safe can be effin painful!!!
Nishant Sivakumar wrote: I can tell you this. Restoring a DB with source safe can be effin painful!!! Sourcesafe sucks. I can't believe that MS still ships this piece of crap with VS. Contrary to their "dog food" policy, not even them use Sourcesafe anymore. I see dead pixels Yes, even I am blogging now!
-
Nishant Sivakumar wrote: I can tell you this. Restoring a DB with source safe can be effin painful!!! Sourcesafe sucks. I can't believe that MS still ships this piece of crap with VS. Contrary to their "dog food" policy, not even them use Sourcesafe anymore. I see dead pixels Yes, even I am blogging now!
Daniel Turini wrote: Sourcesafe sucks. I can't believe that MS still ships this piece of crap with VS. Contrary to their "dog food" policy, not even them use Sourcesafe anymore. I feel that way now too - my first experience with it is not going to be a pleasant memory that I'll treasure for the rest of my life :-)
-
Is it really important to install Subversion first ? I did it.. but i didn't really needed it (altough if I'd use backup and other commands not handled by Tortoise SVN)
All the label says is that this stuff contains chemicals "... known to the State of California to cause cancer in rats and low-income test subjects."
The only thing I could find at their site was this: Do I need to install Subversion in order to be able to use TortoiseSVN to access SVN repositories? Submitted by steveking on Tue, 2005-05-17 20:52. No. TortoiseSVN comes with everything you need to access a repository. Only if you want to set up a server then you will need the Subversion package. I can't see any other way of performing a backup aside from using svnadmin.
:suss: Pssst. You see that little light on your monitor? That's actually a government installed spy camera. Smile and wave to big brother!
-
The only thing I could find at their site was this: Do I need to install Subversion in order to be able to use TortoiseSVN to access SVN repositories? Submitted by steveking on Tue, 2005-05-17 20:52. No. TortoiseSVN comes with everything you need to access a repository. Only if you want to set up a server then you will need the Subversion package. I can't see any other way of performing a backup aside from using svnadmin.
:suss: Pssst. You see that little light on your monitor? That's actually a government installed spy camera. Smile and wave to big brother!
Jack Squirrel wrote: I can't see any other way of performing a backup aside from using svnadmin. when using the tortoise SVN client as a standalone, you are in strictly file-mode. You can backup and restort the subversion tree using any file backup routine for Windows. It does not keep files open, just zip it up and go. _________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
Source safe can be local or server, Tortoise CVS offers a local directory version, Tortoise SVN does the same. Subversion can be setup as a local server or remote, so could probably CVS. If you need ease of use, I would say source-safe first because it integrates easiest with VS, then one of the Tortoise versions because it integrates at the folder level with windows. _________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
CVS and Subversion can also be integrated into visual studio. PushOk sells software at very low cost software to do just this. CVS Subversion I have used both enough to determine that they do, indeed, work. I do not really use them because I prefer Tortoise[CVS|SVN] windows explorer integration over visual studio VSS, CVS or SVN integration.
-
Jack Squirrel wrote: I can't see any other way of performing a backup aside from using svnadmin. when using the tortoise SVN client as a standalone, you are in strictly file-mode. You can backup and restort the subversion tree using any file backup routine for Windows. It does not keep files open, just zip it up and go. _________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
Cool. I used to do it that way, then I read the blurb about using svnadmin + hotcopy in the help manual. Didn't realize that doesn't apply for standalone operation. Thanks for the info.
:suss: Pssst. You see that little light on your monitor? That's actually a government installed spy camera. Smile and wave to big brother!
-
Cool. I used to do it that way, then I read the blurb about using svnadmin + hotcopy in the help manual. Didn't realize that doesn't apply for standalone operation. Thanks for the info.
:suss: Pssst. You see that little light on your monitor? That's actually a government installed spy camera. Smile and wave to big brother!
Jack Squirrel wrote: using svnadmin + hotcopy the point of using hotcopy is that in backing up an active service, you must first establish the current "state" of the database. This can be done by locking out all users, or locking states, file by file durin the copy procedure. Although this doesn't truly apply to the subversion or CVS when in a "client only mode" -- it assumes you know what you are doing. In otherwords if you submit a change in client (local) mode only at the same time as simultaneously backing up the source tree -- you will achieve the exact same state of "unknown" for every file backed up. So, yes, you can backup and restore the files easily in client-only mode, as long as you do not try actually using the client at the same time. You being the only user, that is easy. The subversion service does not have that same guarentee, thus "hotcopy". [edit: at least that is my understanding... anyone is free to correct me.] _________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)