As there are some questions on how to run Ajax.NET on IIS 7 (i.e. Windows Vista) in integrated mode instead of classic mode here are two things you have to check:

1. First check that the IIS_ISSRS group has access to your Web site folder. If you are using the default folder for Web sites with Visual Studio .NET 2005 the simplest way is to add read access at C:\Users\Username\Documents\Visual Studio 2005\WebSites.
2. Run following command to automatic migrate your web.config file:
   %windir%\system32\inetsrv\Appcmd migrate config "<ApplicationPath>"

The breaking change for Ajax.NET Professional is that you have to move the httpHandler (and httpModule if used) to a new section system.webServer and rename httpHandler to handler; next you have to add a name attribute for the handler:

<configuration>

    <location path="ajaxpro">
        <system.webServer>
            <handlers>
                <add verb="*" path="*.ashx" name="AjaxPro" 
                     type="AjaxPro.AjaxHandlerFactory,AjaxPro.2" />
            </handlers>
        </system.webServer>
    </location>

</configuration>

For more breaking changes for ASP.NET 2.0 applications running in Integrated mode read this post.

3 Comments

• Rajesh said Tuesday, April 22, 2008 9:29:48 AM

  Hi, Is there a possibility of running Ajax.NET on IIS7 with classic app pool mode set. Regards, Rajesh

• Michael Schwarz said Tuesday, April 22, 2008 9:58:15 AM

  Hi Rajesh, of course, you're able to run Ajax.NET in classic app pool mode. Regards, Michael

• Walter Gan said Friday, June 20, 2008 11:51:12 AM

  Thanks.Now my web application runs correctly on IIS7.