Windows Phone 7, WP7, Microsoft »

[26 Oct 2010 | 1 Comments]

imageSo this is not breaking news but I was lucky enough to be invited to the Developer Launch party held by Microsoft in central London. This was the real party for those who are really involved in making the phone happen and want to build apps for the phone not the party for those hangers on who were fobbed off with this party ;-)

I had a great time, met a load of interesting people doing interesting things for Windows Phone 7 and I managed to get a few sound bites of video from some of them which I have edited together for your viewing enjoyment!


My Windows Phone 7 Developer launch party experience!


Many thanks to @will_coleman and his team for making everything happen and I am really looking forward to the future!


[13 Oct 2010 | 0 Comments]

I’ve just discovered something that I really really don’t like about Microsoft CRM 4. This is that creating some custom workflow activities that are used in a Crm Workflow means they are linked together forever and ever by version numbers.

I was getting this error message:


After some investigation it turned out that it was because I had changed the version number of the assembly that contained the custom workflow activities which meant that I could no longer publish the workflows that use them. When I try I get this error message.

The answer is to manually set the version number of the dll back to what it was when the workflows were originally published which is just silly.

For a much more detailed look at this problem I found this fantastic article by Eric Bewley.

Software Developement »

[7 Oct 2010 | 1 Comments]

We have recently upgraded our development environments on my project to match the production environment which is running on a 64bit servers. There was a big gotcha which was the delayed signed dll’s in the dev environment were chucking a “Strong name validation failed” error when they were accessed.

There are well documented solutions around using the following command

SN.exe -Vr *,*

However this did not work on the 64bit computer because SN.exe is a 32bit program and put the entry in the 32bit part of the registry. So I moved the registry key this tool enters and put it in the 64bit part of the registry and then everything worked.


Hope that helps some people out there ;)