Then something changed on the machines at work and my machine became very, very unstable with crashes and slow-downs and all manner of unacceptable behaviour. I'm not going to blame SlickRun for that, it's more likely that something else on my machine was conflicting with it and causinf the crappy behaviour. However, without knowing what that other thing was, it was easier to just stop using SlickRun than try and find the real culprit, which I almost certainly could have done nothing about anyway.
So I removed SlickRun and got my system back but I was not happy with the situation. The spoiled kid in me kept whining "where's my SlickRun, I wan't my SlickRun!" The analyst in me would reply "No, you can't have it. We need a stable system at work."
Finally, the Dad part of me got sick of the squabling and said "why don't we try and make our own?" So I am. Apart from keeping the spoiled kid and the analyst parts of me quiet, it also lets me scratch a huge geek-itch.
So what, you may be asking, does that have to do with the title of the post? Well, I needed to be able to store the code off-site, so I could get to it from home or work and I figured that I may as well try and get source control while I'm at it. So I looked into a couple of solutions:
- SourceForge has many projects on it and lots of them seem to be very happy to be there. But I've heard some real horror stories about SF recently and descided to keep on looking.
- CodePlex looked interesting, but at the moment still seems to be in beta and requires that each project is screened by an administrator. I needed to be up and running quicker than that, so also no-go.
- GotDotNet was a no-go from the start. I tried creating a project there a while ago and it was just too much hassle, with plug-ins and pages that would never finish loading. Also, it seems to suffer from load-problems and other "unspecified" ailments which block people from downloading the code or binaries.
- Google Code Hosting looked interesting. More, it looked very promising. So I set up a project there: QuickRun. It uses SVN for versioning so I can use the very good tools that alredy exist for that, such as AnkhSVN or TortoiseSVN. There are loads of others here for those who don't use Windows or Visual Studio, but those two do me just fine. It also has a built-in issue tracking system.
I'm very happy with Google Code Hosting so far. It took less than ten minutes to create the project repository, another twenty minutes for me to remember how SVN works (I use VSS at work usually) and a few minutes to upload the code through to the server. And that's it! All sorted, all done. Cool.