Step-by-step IIS configuration guide
- If the following error occurs, go to applicationHost.config file in C:\Windows\System32\inetsrv\config and set overrideModeDefault properties to "Allow" for handlers section :
<section name="handlers" overrideModeDefault="Allow" />
- If the following error occurs,
proceed to ASP.Net component set up:
- Launch : c:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe –i to register the previous ASP.NET installation with IIS
- If authorization are not set yet, activate them :
- Open IIS Manager and navigate to the site to manage.
- In Features View, double-click Directory Browsing.
In the Actions pane, click Enable to enable the Directory Browsing feature .
- If the following error occurs : Error Message : Handler “PageHandlerFactory-Integrated” has a bad module “ManagedPipelineHandler” in its module listInstallation of CGI and ISAPI extensions is required :
- The following errors requires addition of the folder permissionError Message : The current identity does not have write access to ‘C:\Windows\Microsoft.NET\v4.0.30319\Temporary ASP.NET Files’
- Problem with HTTPPost request in IIS71- ASP.NET MVC4 not handling POST requests in IIS7 integrated modeThe default configuration inserts this in the web.config:The problem is the "*." path, If you change this to "*", then all requests will be handled by the ExtensionlessUrlHandler, including those to static files which will not be served anymore. So the solution is: Remove the POST verb from the handler entries and add new entries for the ExtensionlessUrlHandler with the path set to "*" and only for POST requests:Ideally remove the ones you don't need (x86 and x64 in classic vs. integrated pipeline).2- IIS 7 allow POST requests to html filesMaybe 7 routing is different in respect to handing off a POST to an action that has no argument that can accept the post form data.==> For this Reason I prefer working with Windows Azure
