Configuring Windows 7 + IIS 7.5 to work with the Azure SDK

Question

After struggling for over 4 days with getting the Azure development fabric to correctly handle GET, POST, PUT, and DELETE verbs and route them to an ASP.NET MVC application (without returning HTTP 405 - Method Not Allowed), we were finally able to stumble upon the requirements needed to make this work.

1) REMOVE the WebDAV module from IIS via Add/Remove Windows Components.
2) Make sure that HttpRedirection and HttpErrorReporting are enabled.
3) And of course, make sure the rest of the pre-req's are met (ASP.NET enabled, etc.)

Can anybody confirm these steps as necessary on IIS 7.5, and does this match the environment that Azure presents to our application once deployed? There were no issues like this on IIS 7.0...but I have been unable to find any documentation specifically calling these steps out for IIS 7.5 (I can only find information on IIS 7.0).

Thanks...

Answer 1

I assume, you are considering the fact that Web role on Azure platform would be having IIS 7.0 but not IIS 7.5. I am not sure if there are any compatibility issues between IIS 7.0 and IIS 7.5. But it is important to keep that in mind especially when IIS 7.5 is used on DevFabric.

---

Please mark it as answer by clicking on "Propose As Answer", if it helps

Answer 2

Indeed...which is why I'm concerned about "duplicating" IIS 7.0 behavior since all of our dev machines have IIS 7.5 on them. Also, hopefully this will make things easier when the Web roles shift to IIS 7.5.

Answer 3

Hello, actually you're not required to remove WebDAV Publishing. I have it installed on my IIS 7.5, and Development Fabric works fine. But please make sure you've configured to run all managed modules for all requests:

<modules runAllManagedModulesForAllRequests="true"/>

 

 

---

Lante, shanaolanxing This posting is provided "AS IS" with no warranties, and confers no rights.

Answer 4

Yes, we already had the "runAllManagedModulesForAllRequests" set to true...still, with the WebDAV publishing module installed, any use of the PUT or DELETE verbs resulting in an HTTP 405 - Method Not Allowed response. Removing the module was the only way on 7.5 we were able to successfully route these verbs to our MVC app.

Ideas?

Answer 5

This worked for me as well and allows to keep WebDAV functionality if needed

 

• Keep the WebDAV module installed
• In the IIS management console, at the machine level, select the Modules configuration in the IIS section
• Remove the WebDAV module
• For the Web site that does need WebDAV, expand its node, and add it back using the Modules settings

This bug sucks nonetheless :)

 

Answer 6

Currently the Guest OS 1.x does not support IIS7.5 as this is only enabled in WS08 R2. 

OS 1.x currently deployed is compatible with WS08 SP2. 

Even though you have made it working locally, please understand that the components for IIS 7.5 are not available in Windows Azure Guest OS 1.x.