Rory Primrose

Learn from my mistakes, you don't have time to make them yourself

View project on GitHub

Code Contracts and side by side Azure 1.6 and 1.7 SDK

Posted on June 8, 2012

I have installed the latest SDK that came out this morning and I hit a compilation hurdle straight away.

My solution is starting to get to be a decent size with many third party technologies involved, Code Contracts being just one of them. My website project is failing to compile with an issue raised by the code contracts rewriter.


This appears to be a bit concerning because the project itself compiled fine, but the rewriter failed at the tail end of the project compilation. The output window does shed some light on the issue though.

Reading assembly 'Microsoft.WindowsAzure.ServiceRuntime' from 'C:\Program Files\Windows Azure SDK\v1.6\ref\Microsoft.WindowsAzure.ServiceRuntime.dll' resulted in errors.
    Assembly reference not resolved: msshrtmi, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35.
    Could not resolve type reference: [msshrtmi]Microsoft.WindowsAzure.ServiceRuntime.Internal.InteropRoleUpdates.
    Could not resolve type reference: [msshrtmi]Microsoft.WindowsAzure.ServiceRuntime.Internal.RoleStatus.

While there is side by side support for 1.6 and 1.7 SDK versions, this is clearly referencing the old SDK when I want it to reference the latest bits. The 1.7 SDK readme also provides some further insight.

To avoid confusion when you install both versions, the public versions of the .NET assemblies have been changed. Assemblies from November 2011 are typically marked with version 1.0 or 1.1. The June 2012 release assemblies are labeled with version 1.7. This change will require you to recompile applications or to use assembly binding redirects to pick up the new June 2012 assemblies. For more information, see Assembly Binding Redirection.

The part that got my attention was “binding redirects”. Ok, so something is forcing the project to go to the 1.6 SDK. The most likely cause is the specific version property on the reference in the project.


Setting the Specific Version property to False then automatically picks up the 1.7 SDK.


I don’t know why the Code Contracts rewriter doesn’t like the side by side installation, but the project now compiles successfully.