Thomas Ferris Nicolaisen's blog

This is kind of a continuation of my earlier post about my terminal/shell on OS X and Linux . As I was recently preparing for my Git on Windows talk , I naturally started tweaking the setup on Windows as well in the same direction, and I figured I'd share this setup. Installing Git Either go with Git for Windows , or Git Extensions if you want more GUI as well as Visual Studio integration. I personally have grown a distaste for TortoiseGit , as it sometimes locks files in my repositories. But it's supposed to be good otherwise (as an alternative for Git Extensions). Git Extensions During the Git install, you need to select the scary red option , for integrating Git into Windows cmd-line, if you want to use it from Powershell/Console2 (we'll get back to that later). The cygwin-like Git Bash is not sexy. Update (30/4 2012) :  I think you could also  wrap Console2 around Cygwin , although I haven't tried this myself yet. This way you can avoid the scary

I have written this blog post before ! Regardless, this talk, which was cancelled last year, is now back on track for the 24th of April. The rest of this post is basically a copy of the old one, with a few minor updates: It's been a while since I ran Visual Studio on my laptop. In my early university-college days, around ten years ago,  .NET  was just coming out of the oven. We learned algorithms and data-structures doing Java, but when it came down to actual application development, desktop- and web, connecting GUI's with databases, .NET was the thing. I liked it. It was bit of an eye-opener for me, that I could actually use programming for building useful stuff, and not just fantasize about being a game developer. Later on, I fell back into the Java/J2EE world, and rode there for a while. While working for  Objectware 's Java department, it was always interesting to see what the .NET department was up to, and while they were part of them evil scheme of Microsoft