Azure Cloud Service Installation version of Service runtimes


After installing a fresh copy of Orchard 1.7 as a cloud service I got an error of version mismatch of WindowsAzure.ServiceRuntime
I had to put this code in web.config for the project to run
        <assemblyIdentity name="Microsoft.WindowsAzure.ServiceRuntime" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="" newVersion="" />


erik_oppedijk wrote Aug 19, 2013 at 8:06 PM

Maybe it's better to update all azure references to 2.0 in all projects, these are used just in one or two projects (azure.web)

And also the 2.1 azure library is out, so the update should at least target 2.1

erik_oppedijk wrote Aug 24, 2013 at 8:32 PM

The 2.1 support is already fixed in changeset e094066194a6

fotisgpap wrote Aug 25, 2013 at 10:09 AM

  • The build command line tool references the 2.0 Azure tools (AzurePackage.proj)
  • The Orchard.Azure.Web project references various version of Azure tools from 1.7 to 1.9
I would not like to change the references to 2.1 when the build tool is set to build with 2.0

erik_oppedijk wrote Sep 20, 2013 at 11:40 AM

This is fixed in 1.7.1, all is updated to Azure 2.1

gregslater wrote Oct 15, 2013 at 5:11 PM

This is wrong, although 1.7.1 has been updated to use SDK 2.1, the AzurePackage.proj file still builds a package using SDK 2.0 (see below), so when it's deployed the machines don't have supporting DLLs available.

<Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v10.0\Windows Azure Tools\2.0\Microsoft.WindowsAzure.targets" Condition="exists('$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v10.0\Windows Azure Tools\2.0\Microsoft.WindowsAzure.targets')"/>
<Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v11.0\Windows Azure Tools\2.0\Microsoft.WindowsAzure.targets" Condition="exists('$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v11.0\Windows Azure Tools\2.0\Microsoft.WindowsAzure.targets')"/>

erik_oppedijk wrote Oct 16, 2013 at 8:24 AM

The azurePackage.proj (and the build script) have been removed from 1.7.x (changeset 47580564030c)

The correct path is to publish 1.7.1 from the azure solution, after doing a rebuild of the complete project.

Daniel documented this all here:

gregslater wrote Oct 16, 2013 at 10:41 AM

Ah that makes sense, thought I should still use it as it was still there in the 1.7.1 source.