Two lessons from a frustrating Mango submission
I thought I would share two quick lessons today. Learnt while submitting the latest gReadie update to the marketplace.
I thought I would share two quick lessons today. Learnt while submitting the latest gReadie update to the marketplace.
Late last year when I implemented the unread count Live Tile in gReadie I found myself stunned at just how complicated it was. It seemed to me that it would make a lot more sense if I could just whack a [LiveTileUpdater] attribute on a static method in a class and the phone would run that method occasionally.
I was therefore delighted when details about Mango were released as this is basically what Microsoft implemented.
Over the last few weeks I have been doing a complete rewrite of gReadie, my Google Reader client for Windows Phone 7.
The original codebase for gReadie was really quite cluttered, and I wasn’t going to be able to take advantage of the new features Mango enables without pulling it all out and starting again.
With most of the rewrite behind me now, It is time to start putting together a few blog posts discussing the new features I am using and lessons learnt along the way.
I answered a question on StackOverflow yesterday which I am pretty happy with, so I thought I would share the link on here.
The question asks for general advice on how to write and test an ASP.NET MVC 3 website that correctly uses Inversion-of-Control, Unit Testing and Mocking.
Today my post is to announce the release of a small plugin I have been working on over the last few days. It is a plugin for the Glimpse client side debug tool that integrates profiling information from RavenDb.