LightSpeed and Azure

I'm trying to use LightSpeed 4 on Azure. I have a vanilla MVC3 project to which I have added a basic model, config, and the LightSpeedControllerBase. I have configured LS in config and have kept the Medium Trust Compatibility set to false.

In the worker role I set the enableNativeCodeExecution attribute to be true, even though it is supposedly true by default.

As far as I can tell this should be fine for using LS with its optimisations but the web role fails to start upon deployment. I even took the approach of progressively adding features and making changes to find the point at which the deployment failed.

Any thoughts?

Are you sure you've set all dependent assemblies to copy local? (I didn't need to touch medium trust settings or the other flag you mentioned.)

http://stackoverflow.com/questions/5055654/problem-deploying-my-application-to-azure

If that doesn't do it you'll need to enable diagnostics and check the logs. There are many new features here beyond the SO post; check the docs.

I used the add deployable assemblies option from VS2012 SP1.

Update: I'm still investigating but whenever I set the LS context in config the deployment fails - getting stuck in a loop. Moving that to code avoids the problem. I'm trying to track this down.

Let us know what you find. If you are able to send through a repro then we can have a look at we can have a bit more of a poke at this end.

Jeremy

Sorry, been away in Queenstown for a week. Back in Welly.

I'm just testing some scenarios with the latest version of Azure tools. I have noticed some differences between:

• starting with an MVC project and then Azure-ing it; versus
• starting with an Azure cloud service and adding a web role.

I'll get back to you soon. :)

I think I have it.

When I add Mindscape.LightSpeed.Web (so I can use the LS controller base) it introduces a dependency on MVC 2.0.0.0. I can reproduce this in the local dev fabric by uninstalling MVC 2.

Fusion tells me this:

**Calling assembly : Mindscape.LightSpeed.Web, Version=4.0.1351.20441, Culture=neutral, PublicKeyToken=360c8f37b466ebb2.**
===
LOG: This bind starts in default load context.
LOG: No application configuration file found.
LOG: Using host configuration file: 
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config.
**LOG: Post-policy reference: System.Web.Mvc, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35**
LOG: Attempting download of new URL file:///C:/Users/scott/Documents/Visual Studio 2010/Projects/Teto.Azure/Teto.Azure/csx/Debug/roles/Teto.Web/approot/bin/System.Web.Mvc.DLL.
WRN: Comparing the assembly name resulted in the mismatch: Major Version
ERR: Failed to complete setup of assembly (hr = 0x80131040). Probing terminated.

What's odd is that I use a bindingRedirect to force MVC 3.

  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-2.0.0.0" newVersion="3.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>

But it still wants to use MVC 2. Any ideas?

Did you add the redirect to both web.config files? There's another one in the Views directory.

I've added the redirect to both web.config files and an added WaIISHost.exe.config. The same issue of the MVC 2 reference comes up.

I'm running out of ideas, other than to create my own LightSpeedBaseController.

Wow, what a journey!

When I added the View's web.config I neglected to provide the xmlns attribute of the element. This was enough to force the app to use the MVC 2 reference and scupper my use of MVC 3.

Thanks to everyone who helped me get the bottom of this.