I’ve just added some code syntax highlighting to this blog using SyntaxHighlighter and a great how-to article by Scott Dougherty this means that any code I post should look like this:

There are a few bugs at the moment, one being that tiny_mce is stripping linebreaks from the code posting (just a minor one) and the theme somehow removes the line numbers, but I’m sure I’ll find a way around them…somehow.

One of my unpublished gripes with the DotNetNuke blog was that it was a pain to make work with WLW. One of the cool things with BE.Net is that it does work with WLW, not only that but it works well. Setup was a breeze and within 2 minutes I’m now writing my first post, including tags and categories (hit F2 if you’re trying to do that in WLW).

Now this is cool! 🙂

Well my first real post on BlogEngine.Net is…about BlogEngine.Net!

After running the import program from my old DotNetNuke blog I found that the importer had worked, but that the blog entries had not shown up. This was because the cache that BE.Net uses for the XML data files. Since I’m on a shared hosting I couldn’t just run an IISReset.exe, so I obviously needed a work around, and here it is:

I miss WordPress. I miss the fact that it would save my work periodically, and that if my session timed out while the I was writing a blog, it would be there when I logged back in as an unpublished daft. I miss having my categorised posts. I miss having tags to tell me what I’ve written about. Even Google seems to prefer my old blog, old pages that don’t exist are returned where these ones sit in anonymity.

We were integrating a 3rd party product’s web parts with MOSS the other day and came accross an interesting problem. In site editing mode, all the drop down menus would appear for a flash and then go blank. The actual admin pages we were trying to get to would work if you entered them into the browser directly, but that isn’t an easy way to manage the site!

Had an interesting one yesterday, my bosses Vista laptop booted as per normal, making all the right pictures until just before the log in prompt popped up, then a black screen in what looked to be VGA graphics with the white default arrow cursor.

Corrupted graphics drivers, I thought. A quick boot into safe mode…but no, the same black screen and over-sized pointer.

If you’ve logged onto the properties for your IIS install and found that the ASP.NET tab has mysteriously disappered, you can try a couple of things.

Firstly, try re-registering ASP.NET with IIS using the ASPNET_REGIIS.exe located in the .NET installation folder:

When the Dell engineer said “they’ve asked if you can reinstall the OS” my heart sank. Not because I felt like he was weasling out of work - unusually they were very helpful. Not because installing XP is a hard task, I’ve done it over 100 times on all sorts of hardware.

<p>
  <font size="2"><strong>n:\></strong> <em>Aefdisk 1 /delall /formatfat /pri:1024:6 /ext:0:7</em></font>
</p>

<p>
  <font size="2">Woah woah woah! What&rsquo;s all that?! The command runs &ldquo;Aefdisk&rdquo; on&nbsp;hard disk &ldquo;1&Prime;&nbsp;with the &ldquo;/delall&rdquo; flag, which deletes any exisiting partitions, &ldquo;/formatfat&rdquo; which formats the&nbsp;next partition FAT. &ldquo;/PRI&rdquo; is a primary partition, &ldquo;:1024&Prime; is the partition size, &ldquo;:6&Prime; is the&nbsp;hex partition&nbsp;type which in this case is FAT16 >32mb. &ldquo;/ext&rdquo; is an extended partition, &ldquo;:0&Prime; tells it to use all remaining space on the drive, &ldquo;:7&Prime; is the partition type which is NTFS.</font>
</p>

Recently I found the need to retrieve the key from an existing Exchange Server for a reinstall - the software is legally licensed but the key was somehow lost. A trawl through my registry revealed that the key is stored in an obscure place: