Please note I came across a bug in the code, and revised this post on 31/07/2012.

So we’ve rolled out a new build process at work. I’ve started working with a new company, and when I arrived, the build process for a new environment consisted of a 20 page manual somebody had written. The process of putting a build on an environment was slow, the manual had steps missing that everyone just ‘knew’, the process had multiple failure points, and was more or less a complete disaster. Every other release to PRODUCTION would have some release process error that…

Just found out about a good tool that ships with Windows 7.

My client tasked me with upgrading their build server. Today, their platform builds VS 2080 solutions in .NET 3.5 - and I’ve been pushing to upgrade everyone to Visual Studio (VS) 2010 and eventually .NET 4.0. I want to upgrade the server to build a VS 2010 solution in .NET 3.5.

Still working on those jQuery buttons. Trying to update old ASP.Net Webforms using jQuery, Knockout, and Amplify.

While converting ASP.NET Webforms to be more clienty using HTML 5, Knockout, and jQuery, I came across a problem.

My jQuery bug was already documented. :(

I finished up the Nike+ data importer for www.runningahead.com. You can check out the code for the importer at this Github repository:

I love to find bugs in good software! Came across a little jQuery UI bug today. It’s for one browser, but it always excited to be able to create an easy-to-replicate bug. The bug is small - it deals with the buttonset() method.

Is there anything better in life than finding a better way to do something? An easier commute, a better night’s sleep, a tastier cake recipe? In starting the Nike+ importer for www.runningahead.com, I knew I was going to have to deal with a bit of XML. Which used to mean XPath. Not so much anymore. LINQ to XML, you rock my world. It turns XML like this…