Why I'm so Tired (UK edition)

This is a modification of this page that I adjusted for 2012 UK statistics.

I'm tired because I'm overworked. Let me explain...

• The population of the UK is 62 million. 9 million are retired. That leaves 55 million to do the work.
• There are 12 million who are underage or still in school, and 30 people who are still working on their PhD's since the 50's, which leave 42 million to do the work.
• Two hundred thousand are in the Armed Forces, which leaves forty one and a half million to do the work.
• Of this there are 6 million employed by the public sector. This leaves 35.5 million to do the work.
• Now, there are 100,000 people in prisons, so that leaves 35.4 million to do the work.
• There are 1.6 million unemployed, leaving 33.8 million to do the work.
• There are 50,200 people being treated in hospitals, at doctor appointments, or on sick leave today. That leaves just 35,399,999 people two people to do the work.
• You and me.

And you're sitting there playing around on the Internet!

All that time researching the UK figures, and I realised the stats on the original page are completely made up.

SOPA: How to transfer your domains from Godaddy.com

I'm not really fuming about the SOPA issue as I live in the UK, however given the amount of DNS control the US has, it is worth giving a little-bit-of-a-crap about.

If you happen to use Godaddy for your domains, you might be considering moving away from them after it was revealed that they played quite a big part in penning the details of SOPA (mostly for their own business gain).

Here's a great post on how to transfer your domains to Namecheap.com who are against the SOPA legislation. You give the author a referral but that's fine with me. You can also check which big websites still use Godaddy on Byedaddy.org

Spruce 1.1 released

I've just released a new minor version of Spruce - my open source ASP.NET MVC project for Team Foundation Server. The minor increment fixes a few issues, but also (barring bug fixes) ends the development cycle of the project. I'm not planning on adding any new features or support for new work items to Spruce in the future. It's now got support for MS Agile's Bugs, Tasks, Issue work items and doesn't support the other three work items.

I'm hoping we get a pleasant surprise with the next version of Team Foundation Server, with a UI that moves away from the awful Office/OWA style to something that matches modern DVC websites, like you find with Github, Bitbucket and to some degree Codeplex. Infact if they shipped the Codeplex interface with TFS it would be an improvement. I know Microsoft were recruiting for WPF developers for their TFS team so there's promise there, but they're behind the whole Ruby/Google/Amazon/Git/NoSQL crowd in establishing their presence in the format of a diverse online toolset for developers. You get MSDN.com and the MVC team's efforts and that's about it. Appharbor.com and TeamBuild Server are examples of holes that have been plugged by other companies when Microsoft themselves could probably produce an awesome product, instead of being stuck in the early noughties Winforms world and flogging the dead Silverlight horse.

Anyway ranting aside, Spruce can be found at Codeplex.

403 Forbidden errors with ASP.NET MVC 3

Have you just created an ASP.NET MVC 3 site on your local/developer box to use Windows authentication, mapped it correctly and then continually got an authentication box appearing even though you're typing the username/password correctly? And the permissions on disk are fine, you even have everyone mapped to the root folder.

When you cancel, you get a 403.1 or 403.x error. As I discovered this error comes from a security feature of Windows Vista/7 that stops loop back auth checks which essentially cripples your windows authentication settings without changing the registry. It only ever happens when you're testing the site on localhost, or using a domain that's mapped to 127.0.0.1 in your hosts file or DNS server.

There's a support.microsoft.com page about it here, but the most reliable fix is the 1st of the two options. Here's the relevant parts:

In Registry Editor, locate and then click the following registry key: HKEYLOCALMACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0

Right-click MSV1_0, point to New, and then click Multi-String Value.

Type BackConnectionHostNames, and then press ENTER.

Right-click BackConnectionHostNames, and then click Modify.

In the Value data box, type the host name or the host names for the sites that are on the local computer, and then click OK.

To Squarespace.com and Beyond!

As you've probably noticed if you're one of the 10 people who don't browse the site for less than 40 seconds (that's 99% of the traffic), the URL has changed and the design too. I've moved all my content over from the dedicated Win 2008 server running N2 to Squarespace.com, saving me about £25 a month.

I wasn't that keen on the domain name of the old site, and it was hosted on a virtual dedicated server which was a waste of money for the traffic I get. I did consider doing this a few years ago when I moved to N2, but at the time no blog engines had what I needed for the site.

Fortunately they now do, markdown is supported by all blog sites along with some HTML support and generous amounts of bandwidth and disk space. Being able to post your own HTML and upload your own Javascript, XAPs, and tinker with the CSS/JS/HTML is fairly important for a develop blog though, I tried out Posterous, Tumblr, Wordpress-hosted and Typepad and settled with Squarespace as they let you do whatever you want to your site, bar server-side processing. I think Squarespace is probably the slickest CMS system I've used, they've definitely got a good UI team hidden away in New York.

In the site move I've culled the PHP and Perl snippets - no tears shed there - and lost a few of the tools - the syntax highlighter, network tools, google postcode parser and the docy subdomain. There's better tools out there on the web so no real loss.

Apart from the price change, the biggest improvement of my new hosted CMS/Blog setup is not having to worry about backups or downtime. The 'screw this' moment that made me move was my old server's application pools suddenly stopping for a day last month where I couldn't remote desktop in to restart them and a server reboot would've taken 4 hours. It all seemed to be a bit of a waste of my life fiddling with IIS for something as trivial as a blog.

So now I'm all setup and ready to blog, blog, blog - get ready for at least a post a month!

Random photo of the month

One of the posters found at occupy St Pauls.

A new Spruce UI, a big refactor and a release candidate!

It’s been roughly a year since I started the Spruce project, back in November 2010. Over the course of a year it’s had a lot of hold-ups and could be mistaken for yet another open source project where the author excitedly starts the project and then ditches it after about 3 beta releases. It’s also understandably not had much interest – I would guess that small .NET/C++ teams generally use Fogbugz, JIRA and other web-based bug and task tracking tools, while larger teams will either use TFS with the CMMI project type or the Scrum dashboards via tools like Urban Turtle and the Scrum Dashboard, or just Visual Studio.

Click to read more ...

Using Spruce on a different web server from TFS

One of the big issues I’ve come up against when developing Spruce has been using the website on a different web server from the one TFS runs as. By default TFS creates itself as ‘Team Foundation Server’ as a separate site inside IIS. As its API is entirely web services based, this is where your calls are made to, the .NET assemblies simply wrap these HTTP calls up in an easy to use package.

Click to read more ...

TFS Template types

One of the main features of using TFS for bug and backlog tracking is the power it gives you to edit work item templates. A work item is simply a bag of properties/fields grouped together, like a class in C#/Java/every other OO language. You can customise these fields, and you also get a set of core fields, but you also get to choose the workflow of each field. For example you can’t set a bug to closed, before it’s been resolved.

Click to read more ...

A review of Mike Bluestein's Learning Monotouch

I have been lucky enough to receive a review copy of Mike Bluestein’s “Learning Monotouch”. This is a mini review of the book.

Click to read more ...