>IE7Pro – Don’t run IE without it.


If you are an avid Internet Explorer user, one add-in that I’d highly recommend is IE7Pro!

This add-in brings a number of great features to the table including:
– Ad blocking
– Spell checking
– Inline search (This is the same search implementation as FireFox has and after using this the popup search will seem so annying!)
– A whole bunch more!

Do yourself a favour and check it out.


>Imaginet Webcast Series (part II)


Joel has just posted all the details about Imaginet’s free webcast series.

There’s lots of great content in this series so feel free to take in whatever interests you.

We’ll be recording these webcasts and making them available for you to watch whenever you want. As we finish each webcast we’ll post the archived URL and “show notes”.

Stay tuned for more info.

>XUnit.Net’s [Fact] and [Theory] attributes


Following a debate with Dave yesterday I got to thinking (it’s a rare event, and I like to revel in it when it happens). There may be technical reasons why you have to use [Fact] for a “regular” unit test (oh, I know it’s not a unit test, it’s a specification, humour me) and [Theory] for “data driven” tests. But from a usage point of view, why should I care if it’s data driven or not? Wouldn’t it be nice if the test runner would be able to identify a parameterless method and say “hey, this must be a regular unit test”. Also,if the method has parameters it could be smart enough to say “hmm… this must be a data driven test. Do I have any data available?”. If the developer hasn’t provided any data, then the test, I mean spec, fails.

I think I fall on Dave’s side of the argument that this feels like changing somewhat standardized terminology just for the sake of being different (or maybe it’s trendy to keep up with the Ruby folks?).

What do you think, dear reader?

>Resetting the Administrator password on Windows Server 2003


At my work we use Microsoft Virtual PC quite extensively. One of the “fun” things about this is that you end up collecting alot of passwords. Normally I just have a text file in the same directory as my virtual images that reminds me what the Administrator password is.

Today I booted an image and could not remember the password. I started Googling and found a few solutions. I finally found one that was able to blank out the Administrator password. The project is called Trinity Rescue Kit. It is a bootable Linux ISO image. Once it boots you simply execute “winpass” and follow the prompts. It gave me some scary warnings saying that the filesystem was in use (because I wasn’t able to shut down the image cleanly because I couldn’t log in) and because something called SYSKEY was enabled. I forced a mount of the filesystem and that turned out fine. I also choose the default option for the SYSKEY question (which left it enabled) and that in the end I can now log into the VPC.

Hurray for Trinity Rescue Kit!

>Setting sort order in Windows Live Messenger History


I use Windows Live Messenger quite a bit (for personal and work use actually). I find that it’s annoying that when I view the message history for a contact that it’s sorted with the oldest messages at the top. Most often I’m interested in the newest messages when I go to view message history. Today I decided to change that.

First some background. Windows Live Messenger stores each contact’s message history as an XML file in “My Documents” (or “Documents” if you are on Vista) within a folder named “My Received Files\[msnid]00000\History” (where [msnid] is your Live Messenger id and the 0’s are some number that changes). Within this folder there is also a file named MessageLog.xsl. This file is used when viewing the message history to format the XML files in a nice format (using an XSL transform).

It turns out that it’s very easy to change the ordering of the message history. Within MessageLog.xsl there are several parameters (at the top of the file) that control the layout of the history view. Simply edit the <xsl:variable> named “MostRecentSessionFirst” and set it’s value to 1 your messages will now sort in descending chronological order.

<xsl:variable name=‘MostRecentSessionFirst’>1</xsl:variable>

There’s several other <xsl:variable>’s at the top that you can play with. I’d recommend making a backup before starting to play with this file though.