Sorry for the ungrammar in the thread title but anyway, I'm wondering if there is some tool I can use to either automatically, or easily, make a new backup of the Visual Studio Express 2008 solution I am working on.
I'm looking to store these locally. I know I could look into something like subversion and dropbox but I'm mainly just looking to export the solution to another folder/hard drive with a version number or something, without having to manually copy the folder each time.
Is there any easy to do this? I'm still in the learning stages so I keep trying vastly different things as I go along with my project. Looking at reams of commented-out code just gives me a headache so I'd rather overwrite my old work when trying a different programming tactic, but I'd rather not lose the old work either just in case I need to revisit it later in the project.
I dunno, maybe I'm being too anal. Question remains though.
Switch: SW-7690-2320-9238Steam/PSN/Xbox: Drezdar
Drez on
0
Posts
KakodaimonosCode fondlerHelping the 1% get richerRegistered Userregular
edited July 2010
This is something every professional developer learns to do when they start. It's called "version control" or "source control"
Use actual version control. It's harder to get setup than any funky custom setup you want to do exactly what you want, but it makes it much easier later on.
You should use Git or Mercurial. I was in the subversion camp for a while, I didn't really see what distributed revision control did for me, then I switched to distributed and holy shit it's so much better.
Mercurial is probably the better beginner choice, and maybe easier to set up on Windows (tortoise HG is kind of haphazard, but a nice tool once you get the hang of where things are). You want to know how to work it on the command line before you move up to a GUI tool though.
Thanks guys and gals. Lots of conflicting suggestions. Considering I'm the only person working on this project, would you recommend one over another? It's not going to be a shared project, I basically just want to store versions of my code as I go along.
In the meanwhile, I'll read up on all the suggestions made.
I use Git and I'm the only person on my projects. Shit, I even put papers longer than 4 pages into Git repositories. It's just much safer. I also like Git's branch merging for doing new features, I've never had it barf like Subversion et al. might.
I like SVN. It's most useful for when you are working with others, but still great for your purpose. There are two plugins for Visual Studio that add an SVN interface, Visual SVN (which I've used and is great, but costs $50) and AnkhSVN (which I haven't used but is free!).
Once you roll with source control, you'll never go back! Count my vote towards Perforce for general source code and asset control. For context, I'm a single developer working on an indie game (and general tech platform) which I've been tinkering around with for a couple years now, and during this time, Perforce has adequately served all of my backup and version-ing needs. As far as I recall, Perforce also adds its Visual Studio plugins automatically on installation.
Cathode on
"There is enough light to enlighten the elect, and enough darkness to humble them."
Thanks guys and gals. Lots of conflicting suggestions. Considering I'm the only person working on this project, would you recommend one over another? It's not going to be a shared project, I basically just want to store versions of my code as I go along.
In the meanwhile, I'll read up on all the suggestions made.
Thanks again!
Git or Mercurial don't require you to set up any kind of server - all the old revision information goes inside a hidden folder in the project folder (compressed of course), so that's probably ideal, apart from the lack of Visual Studio integration.
Yeah, subversion is nice and simple, but these modern distributed systems with decent branching and merging and local repositories are so much better - and simpler to set up and start using.
VSE2008 integration is nice but I guess not totally necessary. Hmm. I have to do more research on all my options today. I think I'm leaning toward Git/Mercurial/Perforce.
Posts
Here's an introduction to the basic concepts:
http://betterexplained.com/articles/a-visual-guide-to-version-control/
We use Subversion where I work.
http://www.west-wind.com/presentations/subversion/
For Visual Studio, there's also Team Foundation Version Control, which is not free. And do not use Visual Source Safe, ever.
That's probably enough to get started with.
ohhh and windows mercurial
bitbucket is popular
"Thoughts are a persons imagination going rampid…" - ME
http://code.google.com/hosting/
Check out http://github.com/Lewisham/ for an example.
Use actual version control. It's harder to get setup than any funky custom setup you want to do exactly what you want, but it makes it much easier later on.
Mercurial is probably the better beginner choice, and maybe easier to set up on Windows (tortoise HG is kind of haphazard, but a nice tool once you get the hang of where things are). You want to know how to work it on the command line before you move up to a GUI tool though.
In the meanwhile, I'll read up on all the suggestions made.
Thanks again!
also:
http://book.git-scm.com/1_welcome_to_git.html
And as for SVN servers... you can set up a local repository on your machine. I don't even know why that's a thing.
Git or Mercurial don't require you to set up any kind of server - all the old revision information goes inside a hidden folder in the project folder (compressed of course), so that's probably ideal, apart from the lack of Visual Studio integration.
Yeah, subversion is nice and simple, but these modern distributed systems with decent branching and merging and local repositories are so much better - and simpler to set up and start using.
VSE2008 integration is nice but I guess not totally necessary. Hmm. I have to do more research on all my options today. I think I'm leaning toward Git/Mercurial/Perforce.
Ooh, Perforce seems nice.
http://hginit.com/top/
It's a great introduction to mercurial by Joel Spolsky, who's a great source of information about general development as well.
git is just fine
we also talk about other random shit and clown upon each other