Roberto Bonini

"Developers, by definition, are engineers lost in the details of implementation"

Paul Ford: What is Code?

Both Phil Haack and Jon Gruber linked to this post today.

And with good reason. Its exquisite, sublime (in the OED sense of the word not the IDE), faciniating and insightful in ways that only reading it will adequately communicate.

Paul Ford's Magnum Opus - What is Code?

It should be required reading for anyone involved in anything to do with Software.

PS - Took me 107 minutes (and two cups of tea) to read all 38000 words


Quote of the Day - @SlexAxton

A Microsoft engineer could say "I like meat" and somebody would blog about how Microsoft just declared war on Buddhism

-Alex Sexton on Paul Thurrots blog post The Last Version of Windows?


Great Scott !!


(via CommitStrip)

For the record, I don't torrent......


Windows Server 2012 Essentials - "Restore Files Wizard Has Stopped Working"

Isn't annoying when you really REALLY neeed to restore one critical file and you run into a brick wall?

Fear not! The suggested remedy is to uninstall KB3023562 from all client PCs.

And it worked for me as well :)


I want Tea

Funny (and true):



Update for Windows Azure Backup for Windows Server Essentials 2012

I've been running Windows Home Server since its second beta - away back in 2007. Man, how the time flies!

Last year I moved over to Windows Server 2012 Essentials running on a nice new Dell box with some oopmh.

In October I decided to enable Windows Azure Backup as an experiment - mainly to see the price. I was never going to be able to afford all 5Tb of data being in the cloub, so I started with just 300Gb.

It seems to be about £45 a month, tho its been both more and less.

Starting April 1st ( no joke) the pricing structure has been changed. It should now be cheaper to store the same amount of data. Based on the Windows Azure Pricing Calculator my bill should be cut in half, almost.

However - there is a catch - you have to update the Microsoft Azure Recovery Agent to take full advantage of the lower prices.

When I ran the update, I got this:

The Microsoft Azure Recovery Services Agent installation has failed.

Error : Failed to install Microsoft Azure Recovery Services Agent.

Problem : 1603:Fatal error during installation

The accepted solution seems to be to uninstall Microsoft Azure Recovery Services Agent and then re-install.

But, if you're using the Add-In, it gets a bit more complicated than that.


Make sure that you have the Backup Vault certificate from Azure dashboard, and the Certificate that was originally generated when you first installed the agent. And make sure that you remember your 16 charecter pass phrase. Aditionally, go to the Azure dashboard and make sure you allow your server to re-register,

  1. Remove the Addin using the dashboard - make sure the box to remove the agent is also ticked.
  2. Reboot
  3. Re install the Addin using the dashboard. This will also reinstall the old agent, but will leave your server unregistered.
  4. Install the updated agent and follow the instructions in the wizard.
  5. Check in the Dashboard that it is recieving infomation from the new Agent

And you should be done. The new agent will magically remember the previous configuration of your protected files, retention policy and so on.


I would love this!


Shoot, it landed in the golf course. Gonna be hard to get it down the--oh, never mind, it rolled onto the ice hazard. Face-off! "Shoot, it landed in the golf course. Gonna be hard to get it down the--oh, never mind, it rolled onto the ice hazard. Face-off!"


From The Department of Should Have Thought Of This Before

Have You Tried Rebooting? via CommitStrip


Cartoon Of The Day



Entity Framework Tip of the Day

Yesterday, I was doing so some work with EF and ran into something unusual - my navigational properties weren't being populated.

I rechecked my model and the DB schema and eerything was normal.

So it turns out that my entity object had just been inserted earlier in the procedure. This makes sense becuase EF usually does the navigational property population when you pull an entity directly from the DB.

So - either I find a solution or re-write my method to pull down the recently inserted entity again after insertion.

It turns out there is a single line of code that will fix everything:

Entities.Entry(item).Reference(c => c.NavgationProperty).Load();

This forces EF to load the property using the defined FK - and then using that navigational property works as expected. You'll have to do this for each property that needs to be populated.

Hope someone finds this useful.