IIS 6/5 and the Web Connection Managed Module

Setting up the managed module for IIS 5 or 6 requires a bit of work at the moment as the process is not yet automated. The process basically involves disconnecting any of the wc.dll script maps and re-attaching them to the ASP.NET ISAPI extension instead so that requests run through ASP.NET. In addition a couple of changes in the web.config file are required by uncommenting some entries

You will also need to ensure that the .NET 2.0 runtime is installed.

Here's how to set up a new project and switch to the Managed Module:

This basically maps the Web Connection extensions to ASP.NET in your virtual directory, so if the script map is used it will fire through ASP.NET 2.0. Next we'll need to hook up the Web Connection Connector Handler by modifying a setting in web.config (in your Web directory's root).

<?xml version="1.0"?> <configuration> <system.web> <httpHandlers> <!-- pre IIS 7 or IIS 7 in non-integrated mode NOTE: you still need to set up scriptmaps to c:\windows\Microsoft .NET\v2.0.50727\aspnet_isapi.dll --> <add verb="*" path="*.wp" type="Westwind.WebConnection.WebConnectionHandler,WebConnectionModule"/> <add verb="*" path="*.wc" type="Westwind.WebConnection.WebConnectionHandler,WebConnectionModule"/> <add verb="*" path="*.wcsx" type="Westwind.WebConnection.WebConnectionHandler,WebConnectionModule"/> <add verb="*" path="*.wcs" type="Westwind.WebConnection.WebConnectionHandler,WebConnectionModule"/> <add verb="*" path="*.wwsoap" type="Westwind.WebConnection.WebConnectionHandler,WebConnectionModule"/> <!-- End pre IIS 7 --> </httpHandlers> </system.web> </configuration>



  Last Updated: 2/24/2008 | © West Wind Technologies, 2008