Updating Assembly Versions During TFS Builds

An article of mine has been published on CodeProject - http://www.codeproject.com/Articles/705482/Updating-Assembly-Versions-During-TFS-Builds.

In this article I explain how to modify the AzureContinuousDeployment workflow so that your hosted builds version stamp (i.e. update things like the revision number in the build number to correctly reflect your changeset number); however, this approach can easily be adapted to fit an on-premise TFS installation.

Using the AzureContinuousDelivery Build Process Template on your own server

Wanting to deploy to Azure using Continuous Delivery but not use the Visual Studio Hosted Build servers?

No problem; but you need to install the right version of things first!

I installed:


I then installed a couple of the assemblies from the Azure SDK Lib's into the GAC; these get installed into C:\Program Files\Microsoft SDKs\Windows Azure\.NET SDK\v2.0\ref, and I installed:

If you don't do this, you get an error during the deployment portion of the workflow.

If you try it, let me know how you get on!

Visual Studio 2013 - Feedback tool

Those of you that use Visual Studio in a medium to large company that's worried about data security need to consider the addition of the Feedback tool that Microsoft are bundling with Visual Studio.


While I do applaud Microsoft for apparantly wanting to engage more with people who actually use their product, I have to worry about this feature.




Simple. It takes screenshots - and not just limited to the Visual Studio windows which would be bad enough in some circumstances, but all your desktops.



The good news is you can disable it pretty easily. The bad news is you'll have to ensure a registry key deletion occurs every time a user logs on to your network, as I've seen it occasionally reappear. Nightmare; no easy way to remove it centrally, block it or otherwise censor. Not ideal for an enterprise.

How do you drop this item from the menu?

Delete this key:


Are Microsoft loosing their way with user experience?

Over the past few months there has been a fair bit in the industry press about Apple and Microsoft apparently loosing their respective grasps on the market.

Apple has been (from what it appears) struggling to get a new product into the market, and is instead just refreshing existing lines.

Microsoft is slipping in its game too - the latest gaff has to be the way it's handled Windows 8.1. The recent U-turn about not releasing the RTM version to the development and sys admin community was welcome, but it is a disagreeable find to discover that you can not do a straight upgrade of Windows 8 to 8.1. Instead it enforces a clean install, while offering you the ability to save your files. According to all the recent MSDN coverage (literally in the last 24 hrs or so), the "release" version will support this, but I have to ask why Microsoft decided to release essentially an incomplete version?

Historically the whole idea of RTM or Gold copies were that these were the images that were sent for physical manufacture. These days things still follow this pattern, but now companies such as Microsoft tend to "tweak" things before they are actually released - in theory to provide a better quality product, but in this case you have to wonder. Releasing an incomplete, inferior product a month before the General Availability is annoying, and down right disruptive to the development community. Microsoft's attitude? It doesn't matter. You shouldn't be using this release for anything except testing, so why can't you build a new machine. 

Has the development industry lost track of what should happen for release cycles? Are we now expecting too much, too quickly from software companies?

Or have the big boys (Apple and Microsoft for example) started to loose their way with handling user experience?

Good Customer Service - customer no longer always right?

I'm sure it wasn't that long ago that companies treated customers with respect - and went by the saying "The Customer is Always Right". 

Well it doesn't seem that this is the case any more after a few different retail experiences - I can see why people are starting to do everything online if they are anything to go by.

My most recent "poor" experience is with one of the largest technology companies on the high street. Apple.

I purchased a high end (as in top of the line but one) Macbook Pro Retina 15 online. And had the machine for a week. All was well.
Then it developed a hardware fault. After discussing it with a technical support representative, it was decided that the best course of action was to swap the machine in-store due to the fact it was so new, developed a fault, and that returning it via courier was going to be awkward (my current situation with my son means I'm not home much ... and never during the week at working hours!). And so a 110 mile round trip the Apple store began.
The Apple store in question, Newcastle Metro Centre, didn't have my exact model in stock - but had the marginally newer one, with its grand total of 0.1Ghz faster CPU.
But because I had purchase the machine online they were unable to swap it for this newer SKU. Nor were they able to take it in to return it to Apple for repair on my behalf. All they could do was to "attempt to repair it in-store". Note the word attempt in there. Not overly spectacular considering the cost of the machine in the first place, nor what the technical support rep said, or the fact that Apple seem to make a deal of saying they offer "excellent customer service". Perhaps they do, if you purchase in store - it seems that if this had been the case the machine would have been swapped no questions asked. 

So how do Apple justify this difference between in store and online? They trade as different companies. One for Apple Retail, and one for Apple online - so why do they get away with trading under the same brand? It all seems like it is intended to just confuse members of the public, and I have to admit I did find it confusing - they are the first company that I've come across that have this disparate split between online vs retail.

Developers ... why do we insist on build vs buy?

I've recently been in this situation a couple of times - looking at either writing something myself to solve a problem, or purchase a product off the shelf to either integrate or run alongside my package.

The first time, when the project was something that I am solely involved in, I decided to go down the "do it yourself" route. This was more optimal for me as simply there was no time constraint, and no specific (immediate) financial cost to me putting in "just enough" functionality.

However just today I saw the other situation. A development team whereby they are looking to spend significant time on building functionality they could easily purchase pre-built from a third party vendor. And in this case, it would work out EXACTLY the same price as the estimated hours -- and this doesn't even include any "fudge factor", maintenance or the never ending tweaks that would be needed. And yet as developers we tend to do this so often - instead of realising that it is not always the best way, we push forward and insist that we can come up with something better.

Perhaps it is time that we stepped back and realised that it might actually not be a good idea to write this complete stack of support tools, and instead look to see what is there already? After all, we do purchase SQL Server and Windows Server ... or perhaps we should write our own replacements for these too ...

Fundraising for Yorkhill Childrens Hospital in Glasgow

Back in November my son was born with a Congenital Heart Disease called Fallots Tetralogy. Within 24 hrs of his birth, he was rushed to Yorkhill Hospital in Glasgow and stayed in the Neonatal Intensive Care Unit for a week - and made excellent progress with the amazing staff there. Originally the prognosis was good - after numerous hospital appointments, his first surgery was scheduled for February - and Christmas approached.

Two weeks before Christmas, Toby started getting exceptionally unsettled, and started having 'tet' spells (lack of oxygen causing agitation and black outs) and we had to rush to the local hospital. Immediately he was transferred back to Yorkhill Hospital - exactly a month after being discharged home the last time. His surgery was brought forward. On Christmas Eve, at 08:30, he went down for open heart surgery to correct a number of defects with his heart: to close a large hole in his heart, to insert a pulmonary value and to rebuild his pulmonary artery tree. The heart surgery was an amazing success, and although further complications have developed Toby continues to make unbelievable progress and will soon be home and no-one would know the difference. There are further surgeries in the future, but the largest hurdles have been overcome - and it is in no small part to the outstanding excellence of the staff at Yorkhill Children’s Hospital.

Back at Christmas, while all this was going on, my brother (Mike) and I discussed how we could go about fund raising for the Yorkhill charity. And he has come up with one of the most audacious challenges yet. Eight hardy souls from Ghekko in Macclesfield have stepped up and are going to take part in the Total Warrior event in The Lake District this August.


I have to admit, I'm fairly surprised that my brother has not come up with something involving motorbikes, but, lets give the Ghekko team some support and raise money for a great cause.


The JustGiving page can be found here.

A Samsung Android 4.1.2 update oddity

The Mrs' Samsung Note 2 had an update from Android 4.1.1 to 4.1.2 delivered the other day. And all hell broke loose.

Wifi stopped working. The Mrs was not amused.

After a lot of faffing around, and debating whether to flash the phone back to 4.1.1 using Odin, I stumbled across a rather strange pattern with this particular problem - it was only hot spots that the phone had been used on previously that had stopped working ...

Renaming our home WiFi hotspot got it working again, but I have to question what is getting stored, even without adding her Google or Samsung accounts back onto the phone after flashing it and a factory reset ...  seems something is lurking somewhere ...

Congenital Heart Defects

I've been quiet for a while - things have been rather mental in the last couple of months.

On the 12th November, our little boy was born. Unfortunately there were problems. He was born with a congenital heart defect - Tetralogy of Fallot. We were initially advised of some of the complications back on the 20 week scan, but we were never told just how bad things could get. All we were told was that there would be a surgery or two, but we were not prepared for just how rapidly things could progress.

Immediately after he was born, he was admitted to Yorkhill Childrens Hospital where he remained in the Neonatal unit for four days. After that he was transferred back to our local hospital.

We finally go him home when he was seven days old ... and what a few days we had. Nothing at all prepares you for being a parent.

Things were going great, we had a few checkups with the doctors, and nothing too untoward was happening.

Until early December. He had an exceptionally bad tet spell (basically a significant, prolonged drop in O2 saturation) - this resulted in us rushing him into hospital in a pretty bad shape on the 15th December. On the 16th, he was back up at Yorkhill. Finally, after much waiting, being mucked around, and generally getting stressed, he has his surgery on the 24th December. Not a great Christmas Eve I have to say, but his open heart surgery was successful and he had a (near) full repair (for now). This comprises of a new pulmonary valve, a complete rework of his pulmonary artery, and a VSD (major hole in the heart) closed.

Things were going great (well, as well as they could after our son having major surgery!), but then we had a blow. Complications. Problems with routing of his arteries had caused pressure on his windpipe - causing them to collapse. Even though they had been moved, the damage had been caused. A tracheostomy was performed, and he was put on a ventilator to deliver constant air pressure - ensuring he could breath.

And that was the state of things. We have finally managed to get him moved to a childrens hospital slightly nearer home, but things are still a struggle. My partner and I are having to under go training on how to change a tracheostomy, look after a ventilator, and ultimately, relearn how to look after our son. Things are tough enough, but ultimately not helped by random members of staff in the hospital making life far more awkward than they need to be.


Nothing prepares you for having a child with a condition such as this. Equally nothing prepares you for being in a hospital specialising in the care for children.

New software ... again

Moved the blog onto new software tonight ... this blog is now running on a (slightly tweaked) version of BlogEngine.NET :)