Deleting a branch in Visual Studio Online using GIT for Windows

When you use GIT branching becomes… attractive, maybe even addictive. Which is fine… then (as happened yesterday) you find that a branch really didn’t help in any way and you would like to delete that branch and pretend it never happened 🙂

I’m using the GIT capability of Visual Studio Online and was stumped with how to delete the branch. I managed to remove it from my local repository with ease – but not from Visual Studio Online.

The solution turned out to be very simple but (to me anyway) was not obvious.

Install GIT for Windows. Fire up the GIT Gui and then select the Delete Branch option from the Remote menu. Simple.


Is Visual Studio 2013 ignoring your .gitignore file?

Well, it was for me. Specifically I wanted it to exclude the nuget packages folder which in theory should have been as simple as uncommenting a single line in .gitignore.

Except… VS2013 (with update 2) insisted on still checking in the packages folder. Odd.

Turns out various folks have hit the same problem and the answer turns out to be pretty simple.

  • Close Visual Studio.
  • Navigate to your .git folder
  • Delete ms-persist.xml
  • Restart Visual Studio

And hey presto, all is well.

If you exclude the packages folder then you also need to enable nuget package restore  – check out this great walkthrough.

Shout out for the Scottish Ruby Conference #scotruby

Back in 2010 I dabbled with Ruby (remember when Microsoft was still doing stuff with IronRuby) and during that period I attended the Scottish Ruby Conference – and thoroughly enjoyed it! I was surrounded by a see of Apple products wherever I sat and stared at very little GUI IDE on the stage (I recall a lot of VIM and Emacs). It was so different from my “day job” and I left with huge respect for the then small but passionate community.

Well, my twitter #scotruby tells me it is on again today. It looks like a beautiful day in Scotland and a big part of me wishes I was there.


Just published my first node.js Windows Azure application

Turned out to be simplicity itself (thanks to this sweet tutorial). Great work team on the Windows Azure SDK for node.js and some lovely Powershell integration.


Which in the management portal shows up as:


Currently running (Thursday 19th Jan 2012) at with the exciting output of:


Related Links:

Do we need another Distributed Version Control System?

Well, the short answer is I have absolutely no idea. I have never used one in anger but have played around with Git and Mercurial. I can say with confidence that I am impressed with the promise of DVCS.

Eric Sink on the other hand (who I came across originally while looking into Micro ISVs) is certain we do need another DVCS – as he has created Veracity and has kindly offered to give out printed copies for free. I just requested mine.

He recently posted (in three parts) a video covering Veracity.

Part one of three

Edd strikes again – IronRuby for Rubyists on InfoQ

Note: Cross posted from IUpdateable from Eric Nelson.


Colleague, friend and generally top guy on IronRuby Edd Morgan has just been published over on InfoQ.

To wet the appetite… a snippet or three.

IronRuby for Rubyists

IronRuby is Microsoft’s implementation of the Ruby language we all know and love with the added bonus of interoperability with the .NET framework — the Iron in the name is actually an acronym for ‘Implementation running on .NET’. It’s supported by the .NET Common Language Runtime as well as, albeit unofficially, the Mono project. You’d be forgiven for harbouring some question in your mind about running a dynamic language such as Ruby atop the CLR – that’s where the DLR (Dynamic Language Runtime) comes in. The DLR is Microsoft’s way of providing dynamic language capability on top of the CLR. Both IronRuby and the DLR are, as part of Microsoft’s commitment to open source software, available as part of the Microsoft Public License on GitHub and CodePlex respectively…


Metaprogramming with IronRuby

The art and science of metaprogramming — especially in Ruby, where it’s an absolute joy — is something that could very easily span an entire article. As you would hope, IronRuby code is fully able to manipulate itself allowing you to bend your classes to your whim just as you would expect with a good dynamic language…


Riding the irails?

So let’s get to the point. I think it’s a solid bet to make that a large proportion of Ruby programmers are familiar with the Rails framework – perhaps it’s even safe to assume that most were first led to the Ruby language by the siren song of the Rails framework itself.

Long story short, IronRuby is compatible enough to run your Rails app…

Now… get yourself over to the full article and also check out some of Edds other work below.

Related Links: