Source Versions?
-
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)