ran through the Ruby Koans

I did most of the Ruby Koans last night and finished it up today.


Most of it felt ‘right’ (at least with my history in perl/python/etc) although a few of them seemed a bit odd (at least in 1.9.3 behavior).

The ones that stuck out as odd (at least, IMHO) were:

array slicing with the first index that is invalid

This is a test that passes:

I’m assuming there’s a particular use case (and/or legacy behavior) behind that, but it seemed odd to me.

‘here’ docs differing based on delimiters

The koans included showing how ruby can do ‘here docs’ (inline multi-line strings) with ‘flexible quoting’ which made them easier to deal with depending on the content of the string.

However, I was surprised to find it gives you different behavior than what would appear to be the equivalent ‘here doc’ since it keeps the initial newline.

Now, I could see this being intentional since the older ‘here doc’ format has been around for awhile, and for the flexible quoting to not include the first newline would seem very odd to those not thinking of it as another form of ‘here doc’ (since the quoting starts before that first newline, after all), but in terms of showing it as “here’s another way you can do X”, it struck me, at least initially, as odd. 🙂

If you like Bo Burnham…

I hope this is just some really good troll.  Otherwise, poor Bo Burnham might be going on a RAMPAGE. 🙂

If anything, I would more expect to see Rucka Rucka Ali listed before Justin Bieber.

Of course, I can’t seem to get Pandora to understand that liking Bo Burnham means I like the music part, since it keeps throwing in regular stand-up acts instead of things like MC Lars, Stephen Lynch or The Lonely Island


Google results with DMCA removal notice

I had never seen this before (or, at least, I hadn’t noticed it before) – a results page that included some text saying that a result had been removed due to DMCA complaint:



Text version:

In response to a complaint we received under the US Digital Millennium Copyright Act, we have removed 1 result(s) from this page. If you wish, you may read the DMCA complaint that caused the removal(s) at ChillingEffects.org.

Unfortunately, the actual notice is apparently still being processed (I guess)



Getting your favorite Visual Studio 2010 extension to run in Visual Studio 11

If there are VS2010 extensions you miss when running in VS11, you most likely can edit the extension metadata and it’ll install and run fine.

Here’s an example – one of my favorite VS2010 extensions is PowerConsole which lets you do VS automation in PowerShell.

Unfortunately, if you download and try to ‘run’ the vsix file (it’s just a zip file with some specific metadata files included and an extension for VS to register 🙂 with a machine with only VS11 on it, you’ll get:


The install log is pretty specific:

4/11/2012 6:57:35 PM – Microsoft VSIX Installer
4/11/2012 6:57:35 PM – ——————————————-
4/11/2012 6:57:36 PM – Initializing Install…
4/11/2012 6:57:36 PM – Extension Details…
4/11/2012 6:57:36 PM –     Identifier      : c0dc615b-6157-4f7f-83fd-90101c4d07d5
4/11/2012 6:57:36 PM –     Name            : PowerConsole
4/11/2012 6:57:36 PM –     Author          : Microsoft
4/11/2012 6:57:36 PM –     Version         : 1.0
4/11/2012 6:57:36 PM –     Description     : An extensible PowerShell command window for Visual Studio.
4/11/2012 6:57:36 PM –     Locale          : en-US
4/11/2012 6:57:36 PM –     MoreInfoURL     : r
e4/11/2012 6:57:36 PM –     InstalledByMSI  : False
4/11/2012 6:57:36 PM –     SupportedFrameworkVersionRange : [4.0]
4/11/2012 6:57:36 PM –
4/11/2012 6:57:39 PM –     Supported Products :
4/11/2012 6:57:39 PM –         Microsoft.VisualStudio.Pro
4/11/2012 6:57:39 PM –             Version : [10.0]
4/11/2012 6:57:39 PM –
4/11/2012 6:57:39 PM –     References      :
4/11/2012 6:57:39 PM –
4/11/2012 6:57:39 PM – Searching for applicable products…
4/11/2012 6:57:39 PM – Found installed product – Microsoft Visual Studio 11 Ultimate Beta
4/11/2012 6:57:39 PM – Found installed product – Microsoft Visual Studio 11 Premium Beta
4/11/2012 6:57:39 PM – Found installed product – Microsoft Visual Studio 11 Professional Beta
4/11/2012 6:57:39 PM – Found installed product – Microsoft Visual Studio 11 LightSwitch Beta
4/11/2012 6:57:39 PM – Found installed product – Microsoft Visual Studio 11 Shell (Integrated) Beta
4/11/2012 6:57:39 PM – Found installed product – Installed Globally
4/11/2012 6:57:39 PM – Found installed product – ssms
4/11/2012 6:57:39 PM – VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.
   at VSIXInstaller.App.InitializeInstall()
   at VSIXInstaller.App.OnStartup(StartupEventArgs e)

To fix, we can edit the extension.vsixmanifest file in the root of the archive

With 7zip, I just had to right-click on the vsix file and do ‘Open Archive’:


Then I could right-click and Edit the file from inside there:


WIth the file open in an editor, add VS11 as supported by adding these lines (copy-paste of existing VisualStudio node for 10.0 and change 10.0 to 11.0)


Now you can ‘run’ the vsix:



and here’s the extension working fine:


using it to open the new project dialog: