Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Choosing VCS for Single Developer, Small Projects, Two PC's, Two Locations

Choosing VCS for Single Developer, Small Projects, Two PC's, Two Locations

Scheduled Pinned Locked Moved The Lounge
collaborationvisual-studiosysadminalgorithmstools
84 Posts 49 Posters 27 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D David Knechtges

    Yeah, since you don't want to use sneakernet for sharing between the two locations and you also want version control, you might want to try and find an online host for it. I use a paid one for my work - beanstalk - and it works REALLY well for our subversion needs. If you need free, there might be some out there, beanstalk has a trial account which is 100MB with 1 user and 1 repository. If that is enough for you, then go for it. beanstalkapp.com You could also use a cloud storage if you just want to shuttle files.

    P Offline
    P Offline
    Preston McCormick
    wrote on last edited by
    #56

    I've used a free Beanstalk account for hobby development the past couple of years. I recommend it. :thumbsup: You can pick between Subversion, Git, and Mercurial. Subversion is more than fine for a single developer. The single repository is not much of a limitation since you can just put each project in a subfolder.

    K 1 Reply Last reply
    0
    • O onemorechance

      I just started using TortiseHG and BitBucket for things away from work. So far, I am quite pleased. The free private repositories was a huge factor in making that choice.

      N Offline
      N Offline
      nedmech
      wrote on last edited by
      #57

      Ditto on the recommendation for Mercurial/TortoiseHg/BitBucket. I played around with Subversion, Git, and Mercurial, and the TortoiseHg setup was the easiest of all of them to get configured on my Windows XP machines.

      D 1 Reply Last reply
      0
      • P PIEBALDconsult

        Personally, what I'd like is some sort of "VCS-on-a-stick" -- have everything on a USB device that can be carried around and used on any (Windows) system where I may need it. :cool:

        N Offline
        N Offline
        nedmech
        wrote on last edited by
        #58

        I keep a copy of my "C:\Program Files\TortoiseHg" folder on my USB hard drive. Of course, the icon overlays do not function from the USB copy; but TortoiseHg has no problems (that I've found) running from my USB copy on machines where I don't already have it installed. The only real problem is that the settings are not totally portable this way. It still looks at the %USERPROFILE%\Mercurial.ini file for the general settings. So I keep a copy of that file in the USB folder as well to use if I need to. -edit- It's not an ideal VCS-on-the-go solution, but it suffices in a pinch if I really need to work with a repository on a machine that doesn't have Mercurial/TortoiseHg installed. -edit 2- I happened to run across some documentation today about how TortoiseHg picks up settings, and it looks like it would actually use my Mercurial.ini file from within the application directory when running from my USB device. It picks up the config file from the app folder first, then %USERPRIFILE% if it exists, then per-repository "hgrc" settings. So my semi-portable USB usage should actually work better than I originally thought.

        1 Reply Last reply
        0
        • P peterchen

          git, becsue - distributed DVCS are addictive - git is the "lowes common denominator everyone agrees on". It's a pain to learn, and both the built-in and the 3rd party visualizations give me UX flinches. Other than that, it does most things right. DVCS gives you rollbacks on stereoids. But that's not the key: they can change how you work with source code.

          FILETIME to time_t
          | FoldWithUs! | sighist | WhoIncludes - Analyzing C++ include file hierarchy

          S Offline
          S Offline
          Stefan_Lang
          wrote on last edited by
          #59

          I wonder: the OP specifically asked about single developer projects, and you suggest and even stress the point of GIT being distributed. Why do you think he needs a DVCS? I mean, I do understand the neccessity of push and pull mechanics in distributed development. But for a single developer, where is the advantage over other non-distributed VCS systems, such as creating a working copy with SVN? Or, more to the point, why would it be worth the extra effort of learning a more complicated VCS? I did ask around a lot, and did read up on the various mechanics. Some operations may be faster, but some will also be slower. But for a single developer, the main difference appears to be the learning curve, and everyone, including GIT protagonists, say that it is very steep for GIT.

          P 1 Reply Last reply
          0
          • M M Badger

            (I couldn't find a better forum for this q, hope it's not out of place) I am a hobbyist just having fun trying to do things that seem interesting, so I have a range of small projects. I work on two laptops at two locations and use a network location at both locations for file storage (network drive at work and a NAS at home) for backup reasons. So, to work on one project I end up shuffling updates back and forth on a USB stick or having to crank up the work laptop at home and connect via VPN just to pull the files. I'd like to be able to use something like a VCS to manage this, recognising (and liking) the extra benefit of being able to rollback to previous versions etc. (fallen foul of this once or twice already). I haven't used SVN, GIT, Bazaar etc. before so I'm not at all familiar (yet) with using them - though I'm happy with the general concept of version control, just not as applied to software development nor doing so via the VCS used in software development. Clearly my preference is for something really simple that does the two jobs I described quickly and easily - (a) make it easy to work on two different devices at two different locations without shuttling USB sticks back and forth and (b) rollbacks. If it has other features then that's great but not if they come at a significant cost in complexity. So, is there anything you could recommend? Or do I need to make some compromises? (Using VS Express so cannot install AddIns but can add menu commands via the External Tools functionality). Thanks, Mike

            R Offline
            R Offline
            Reese Currie
            wrote on last edited by
            #60

            Mike, I've used git and Mercurial to do this successfully. For you as a hobbyist I'd recommend Mercurial over git simply because it's more straightforward to use and has a shorter learning curve. I have to say I liked git a little better than Mercurial for this, but the learning curve is hard to justify if version control isn't your main focus. My model for doing it was having a master repository on one machine and a cloned repository on another, and taking Mercurial patches back and forth as e-mail attachments, on USB, or whatever. This was necessary because the content was work-related and my company does not permit using BitBucket, GitHub or any other cloud repository. If you don't want anyone to possibly see what you're working on, then do something similar to my way, otherwise the suggestions given about using a cloud service are the easiest way to go. Avoid SVN for this task. I manage SVN repositories at work and it is a great tool as a central repository, but it is not a distributed system and it isn't nice about being shoehorned into that role. There is a product called SVK for SVN-style distributed processing but I haven't tried it, because it wouldn't install on Ubuntu because it apparently relies on deprecated Perl libraries. It installs on Windows just fine.

            1 Reply Last reply
            0
            • P PIEBALDconsult

              doc_net wrote:

              break your coding down into small bite-size chunks

              Hear! Hear! In my opinion, that is the most important thing for teams of developers to do. One of the greatest benefits is that it reduces the need for multiple developers to modify the same file at the same time, thereby reducing conflicts and merges. Having a great merge process is good, but avoiding merges is better. This is why C# (and VB.net) should have had partial classes from the beginning.

              S Offline
              S Offline
              Stefan_Lang
              wrote on last edited by
              #61

              PIEBALDconsult wrote:

              teams of developers

              OP wrote:

              single developer

              :doh:

              P 1 Reply Last reply
              0
              • M M Badger

                (I couldn't find a better forum for this q, hope it's not out of place) I am a hobbyist just having fun trying to do things that seem interesting, so I have a range of small projects. I work on two laptops at two locations and use a network location at both locations for file storage (network drive at work and a NAS at home) for backup reasons. So, to work on one project I end up shuffling updates back and forth on a USB stick or having to crank up the work laptop at home and connect via VPN just to pull the files. I'd like to be able to use something like a VCS to manage this, recognising (and liking) the extra benefit of being able to rollback to previous versions etc. (fallen foul of this once or twice already). I haven't used SVN, GIT, Bazaar etc. before so I'm not at all familiar (yet) with using them - though I'm happy with the general concept of version control, just not as applied to software development nor doing so via the VCS used in software development. Clearly my preference is for something really simple that does the two jobs I described quickly and easily - (a) make it easy to work on two different devices at two different locations without shuttling USB sticks back and forth and (b) rollbacks. If it has other features then that's great but not if they come at a significant cost in complexity. So, is there anything you could recommend? Or do I need to make some compromises? (Using VS Express so cannot install AddIns but can add menu commands via the External Tools functionality). Thanks, Mike

                N Offline
                N Offline
                Nji Klaus
                wrote on last edited by
                #62

                I use Subversion and TortoiseSVN for home projects. Simple enough for home use.

                1 Reply Last reply
                0
                • N nedmech

                  Ditto on the recommendation for Mercurial/TortoiseHg/BitBucket. I played around with Subversion, Git, and Mercurial, and the TortoiseHg setup was the easiest of all of them to get configured on my Windows XP machines.

                  D Offline
                  D Offline
                  Daniel Santillanes
                  wrote on last edited by
                  #63

                  You may want to try projectlocker.com Free private svn repositories, a bit limited in space (I think it's 300MB)... but it's been working for me.

                  daniero

                  1 Reply Last reply
                  0
                  • P Preston McCormick

                    I've used a free Beanstalk account for hobby development the past couple of years. I recommend it. :thumbsup: You can pick between Subversion, Git, and Mercurial. Subversion is more than fine for a single developer. The single repository is not much of a limitation since you can just put each project in a subfolder.

                    K Offline
                    K Offline
                    Kar1
                    wrote on last edited by
                    #64

                    I think these are the most popular and I'd recommend Subversion (SVN) which has several interfaces like TortoiseSVN that aren't part of the IDE (VS). Git and Mercurial are better for collaboration and networked environments. Subversion is perfect for small groups or individuals. I don't know if you can put it on a USB but you can run it standalone on one machine. Karl

                    1 Reply Last reply
                    0
                    • G glenner003

                      But it's not because you can't extend VS that you are unable to use a version control system. You can use one from the command line or use a client like tortoise. You'll learn more about source control too.

                      S Offline
                      S Offline
                      salempia
                      wrote on last edited by
                      #65

                      yep used tortoise when i was working from home and it's not that bad

                      1 Reply Last reply
                      0
                      • M M Badger

                        (I couldn't find a better forum for this q, hope it's not out of place) I am a hobbyist just having fun trying to do things that seem interesting, so I have a range of small projects. I work on two laptops at two locations and use a network location at both locations for file storage (network drive at work and a NAS at home) for backup reasons. So, to work on one project I end up shuffling updates back and forth on a USB stick or having to crank up the work laptop at home and connect via VPN just to pull the files. I'd like to be able to use something like a VCS to manage this, recognising (and liking) the extra benefit of being able to rollback to previous versions etc. (fallen foul of this once or twice already). I haven't used SVN, GIT, Bazaar etc. before so I'm not at all familiar (yet) with using them - though I'm happy with the general concept of version control, just not as applied to software development nor doing so via the VCS used in software development. Clearly my preference is for something really simple that does the two jobs I described quickly and easily - (a) make it easy to work on two different devices at two different locations without shuttling USB sticks back and forth and (b) rollbacks. If it has other features then that's great but not if they come at a significant cost in complexity. So, is there anything you could recommend? Or do I need to make some compromises? (Using VS Express so cannot install AddIns but can add menu commands via the External Tools functionality). Thanks, Mike

                        E Offline
                        E Offline
                        etkid84
                        wrote on last edited by
                        #66

                        If I were you, I would try using Git based upon what limited info I have read so far. I use svn at work, and would like to work with Git. I have also used ClearCase, SCCS, and even VDE for VAX/VMS. I am one of these types that finds value in learning how to use a slide rule, square root tables, trig tables, and interpolation before allowing a student to use a calculator. Same for learning assembly language and C, and C++ before teaching a student Java or C#. In fact, the first language I did as a professional was Ada83/95, and I would Ada for a short term project in a heartbeat. If you got this far, and are unsure of your ability -- download TortoiseSVN and use that. It works fine. Good luck, and kind regards,

                        David

                        1 Reply Last reply
                        0
                        • S Stefan_Lang

                          PIEBALDconsult wrote:

                          teams of developers

                          OP wrote:

                          single developer

                          :doh:

                          P Offline
                          P Offline
                          PIEBALDconsult
                          wrote on last edited by
                          #67

                          Yes, I was commenting on the general benefits of smaller files as mentioned in the post to which I was responding.

                          S 1 Reply Last reply
                          0
                          • M M Badger

                            (I couldn't find a better forum for this q, hope it's not out of place) I am a hobbyist just having fun trying to do things that seem interesting, so I have a range of small projects. I work on two laptops at two locations and use a network location at both locations for file storage (network drive at work and a NAS at home) for backup reasons. So, to work on one project I end up shuffling updates back and forth on a USB stick or having to crank up the work laptop at home and connect via VPN just to pull the files. I'd like to be able to use something like a VCS to manage this, recognising (and liking) the extra benefit of being able to rollback to previous versions etc. (fallen foul of this once or twice already). I haven't used SVN, GIT, Bazaar etc. before so I'm not at all familiar (yet) with using them - though I'm happy with the general concept of version control, just not as applied to software development nor doing so via the VCS used in software development. Clearly my preference is for something really simple that does the two jobs I described quickly and easily - (a) make it easy to work on two different devices at two different locations without shuttling USB sticks back and forth and (b) rollbacks. If it has other features then that's great but not if they come at a significant cost in complexity. So, is there anything you could recommend? Or do I need to make some compromises? (Using VS Express so cannot install AddIns but can add menu commands via the External Tools functionality). Thanks, Mike

                            M Offline
                            M Offline
                            Marc Greiner at home
                            wrote on last edited by
                            #68

                            Hi Mike, Have a look at this tutorial for an SVN setup: http://ilmatte.wordpress.com/2008/04/27/guide-to-versioning-a-visual-studio-solution-with-subversion-tortoisesvn-and-ankhsvn/ I followed the instructions, and it works well for me. I use this setup since several years. The AnkhSVN part is for the VS2010 integration, and might not work with the express edition, so just skip it, although it is really nice to have full VS integration with AnhkSVN, this plugin is really top. Notes: - You don't need to set svn as a windows service, as no other PC will need to connect to your local repository. The tutorial explains how to do that, but you don't need it. - The download links mentioned in the article are somewhat deprecated, but it is easy to find the proper links. hth

                            1 Reply Last reply
                            0
                            • B Brisingr Aerowing

                              I use TortiseHG[^] and BitBucket[^] for version control (I have VS 2010 Ultimate, BTW). TortiseHG is kind of finicky to get working, but once you know how to use it, you can get changes pushed online rather quickly.

                              public class SysAdmin : Employee
                              {

                               public override void DoWork(IWorkItem workItem)
                               {
                                    if (workItem.User.Type == UserType.NoLearn){
                                       throw new NoIWillNotFixYourComputerException(new Luser(workItem.User));
                                    }else{
                                         base.DoWork(workItem);
                                    }
                               }
                              

                              }

                              C Offline
                              C Offline
                              computer_nerd
                              wrote on last edited by
                              #69

                              I also use TortoiseHG (the GUI program for use with Mercurial if you don't want to use the command line). Mercurial is a nice easy version control system that is good for a single developer because it's easy to set up. I use it separately from VS2010 and don't really see a benefit in integrating them. See my previous post[^] for more

                              1 Reply Last reply
                              0
                              • D Dave Kreskowiak

                                Since you're using the Express edition of Visual Studio you have no (legal) options at all. There are hacks out there that will get some product here and there to work, but you're violating the license aggreement for Visual Studio Express by doing so. [EDIT] Before everybody else jumps down my throat, I KNOW that there are other solutions to source control that don't integrate with Visual Studio that he can use. This answer was originally intended to handle the case of VS integration ONLY. I should have been more clear. My apologies.

                                A guide to posting questions on CodeProject[^]
                                Dave Kreskowiak

                                R Offline
                                R Offline
                                Rob Grainger
                                wrote on last edited by
                                #70

                                Simply wrong, you just won't be able to integrate source control inside visual studio. Using any of the non-Microsoft SCC systems, the tools can be applied at the command-line. Using tools such as Tortoise SVN give Windows Explorer integration, which can help those with command-line-phobia.

                                D 1 Reply Last reply
                                0
                                • P PIEBALDconsult

                                  peterchen wrote:

                                  can change how you work with source code

                                  I see that as a bad thing.

                                  P Offline
                                  P Offline
                                  peterchen
                                  wrote on last edited by
                                  #71

                                  Please Explain.

                                  FILETIME to time_t
                                  | FoldWithUs! | sighist | WhoIncludes - Analyzing C++ include file hierarchy

                                  1 Reply Last reply
                                  0
                                  • S Stefan_Lang

                                    I wonder: the OP specifically asked about single developer projects, and you suggest and even stress the point of GIT being distributed. Why do you think he needs a DVCS? I mean, I do understand the neccessity of push and pull mechanics in distributed development. But for a single developer, where is the advantage over other non-distributed VCS systems, such as creating a working copy with SVN? Or, more to the point, why would it be worth the extra effort of learning a more complicated VCS? I did ask around a lot, and did read up on the various mechanics. Some operations may be faster, but some will also be slower. But for a single developer, the main difference appears to be the learning curve, and everyone, including GIT protagonists, say that it is very steep for GIT.

                                    P Offline
                                    P Offline
                                    peterchen
                                    wrote on last edited by
                                    #72

                                    Fair Question. Three reasons: 1. He's a developer with two locations already 2. It's the future 3. It's not just branching An external site like github can act as both sync point and backup. Now, normally you would start every session with a fetch, and finish it with a push. However, life isn't always so forgiving. Having no internet access to fetch, or having to leave without time to push, you can still work decently and integrate distinct branches through rebasing later. In my myopic view of the world, DVCS are the future. Their only downside is the learning curve. Ubiquitous internet access enables distributed development, and we know that - set up correctly - it's no less efficient than a cubicle mosh pit. DVCS deals with the connection problems. That makes it a decent plus if you join a team or find a coding buddy next town.


                                    On the "It's not just branching" I am walking out on a limp here. My experiences with subversion were back when it was "VSS without the stigma"*. Do I need branches? My attitude went from "branch if you need" to "branch if it helps". The effort (in planning, remembering, considering, merging) becomes trivial. The kicker, though, is that logically you don't work with revisions anymore, but with changes: Branches don't "own" code anymore, they are just containers for different aggregations of functionality. Functionality can can be moved around and regrouped, bug fixes copied to another branch, "Work In Progress" and incomplete ideas are not just "safely stored", but can be kept close to your main branch. Being able to reorder and group commits before they are published solves for me a conflict between "commit offen for easy undo" and "publish a clean, readable history." It also acts as a small "self code review" of my last batch of work. Does a solo developer need a DVCS? No. I freely admit: getting started with git hurt me a lot - luckily I had someone holding my hand (though cp & stackoverflow can give you necessary answers reasonably quickly). However, OP is in a perfect situation to learn tools of the trade - not just what's the minimum necessary to swing by. *) slight exaggeration for artistic purposes. Maybe SVN now allows similar - I honestly can't tell. Even then, the other two poins kind of make it up

                                    FILETIME to time_t
                                    |

                                    S 1 Reply Last reply
                                    0
                                    • R Rob Grainger

                                      Simply wrong, you just won't be able to integrate source control inside visual studio. Using any of the non-Microsoft SCC systems, the tools can be applied at the command-line. Using tools such as Tortoise SVN give Windows Explorer integration, which can help those with command-line-phobia.

                                      D Offline
                                      D Offline
                                      Dave Kreskowiak
                                      wrote on last edited by
                                      #73

                                      I know there are other solutions that don't integrate with Visual Studio and I know how this answer was worded would imply that I didn't. Look at the other answer to the OP here[^] and you'd know that.

                                      A guide to posting questions on CodeProject[^]
                                      Dave Kreskowiak

                                      1 Reply Last reply
                                      0
                                      • G glenner003

                                        But it's not because you can't extend VS that you are unable to use a version control system. You can use one from the command line or use a client like tortoise. You'll learn more about source control too.

                                        D Offline
                                        D Offline
                                        Dave Kreskowiak
                                        wrote on last edited by
                                        #74

                                        I know how the thread started seems like I was saying he couldn't use source control at all. My original reply should have been more clear, but was limited to source control solutions that tried to integrate with VS. My apologies.

                                        A guide to posting questions on CodeProject[^]
                                        Dave Kreskowiak

                                        P W 2 Replies Last reply
                                        0
                                        • P PIEBALDconsult

                                          Then explain Subversion, et al.

                                          D Offline
                                          D Offline
                                          Dave Kreskowiak
                                          wrote on last edited by
                                          #75

                                          Read the edit... http://www.codeproject.com/Messages/4267348/Re-Choosing-VCS-for-Single-Developer-Small-Project.aspx[^] and http://www.codeproject.com/Messages/4267410/Re-Choosing-VCS-for-Single-Developer-Small-Project.aspx[^]

                                          A guide to posting questions on CodeProject[^]
                                          Dave Kreskowiak

                                          1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • World
                                          • Users
                                          • Groups