Quantcast
Channel: West Wind Message Board Messages
Viewing all articles
Browse latest Browse all 10393

Re: web.config vs. wc.ini

$
0
0
Re: web.config vs. wc.ini
Web Connection 5.0
Re: web.config vs. wc.ini
Apr. 19, 2013
05:52 pm
3RK12AXRLShow this entire thread in new window
Gratar Image based on email address
From:Rick Strahl
To:Stein Goering

Yes that's about it.

You DO need to add the script mappings into the web.config file. The mappings point each script map at the Web Connection Module.

<system.webServer><httpErrors existingResponse="PassThrough" /><!-- IIS 7 Script Map Configuration --><handlers><addname=".wc_wconnect-module" path="*.wc" verb="*" type="Westwind.WebConnection.WebConnectionHandler,WebConnectionModule" preCondition="integratedMode"/><addname=".wcs_wconnect-module" path="*.wcs" verb="*" type="Westwind.WebConnection.WebConnectionHandler,WebConnectionModule" preCondition="integratedMode"/><addname=".wcsx_wconnect-module" path="*.wcsx" verb="*" type="Westwind.WebConnection.WebConnectionHandler,WebConnectionModule" preCondition="integratedMode"/><addname=".wwsoap_wconnect-module" path="*.wwsoap" verb="*" type="Westwind.WebConnection.WebConnectionHandler,WebConnectionModule" preCondition="integratedMode"/><addname=".wwd_wconnect-module" path="*.wwd" verb="*" type="Westwind.WebConnection.WebConnectionHandler,WebConnectionModule" preCondition="integratedMode"/><addname=".blog_wconnect-module" path="*.blog" verb="*" type="Westwind.WebConnection.WebConnectionHandler,WebConnectionModule" preCondition="integratedMode"/></handlers></system.webServer>


etc.

You can look at the generate maps in the new project to see exactly other things are needed in your web.config file.


+++ Rick ---


Rick,

Can you provide a quick step by step for converting an existing ISAPI setup to the managed module? (What I found in the docs addresses setting up a new project to run under the MM.)

This is under IIS7 on Server 2008 so I already have a web.config file in wwwroot pointing my script maps to wc.dll. Do I just modify (or replace) those to follow this format?
<add name="*.wc_wconnect" path="*.wc" verb="*" type="Westwind.WebConnection.WebConnectionHandler,WebConnectionModule" preCondition="integratedMode,runtimeVersionv2.0" />

I would then add <webConnectionConfiguration> and <webConnectionErrorPages> sections that replicate my wc.ini settings.

Finally I need to copy WebConnectionModule.dll to the server - since the above mapping are defined in the root, do I make a bin folder under wwwroot for it?

Am I missing anythng? I gather that I don't have to explicitly register the dll - how does IIS recognize it given that there's no mapping that points directly to the file location?

--stein


Hi Kirk,

If you're running ISAPI the INI file is used for Web Connection settings. If running the managed module web.config is used for Web Connection settings.

For development with Visual Studio web.config is used to hold some environment settings - those settings are not required at runtime.

However, IIS 7 stores virtual directory configuration information in web.config. So even if you're running ISAPI, any IIS settings like script maps, permission settings (anything from the Managemnet Console) will end up in Web.config. On IIS 7 you will most likely have a web.config file, but if you're using ISAPI messaging no Web Connection settings are stored there.

This is actually a very good thing although it can seem confusing. On IIS 7 all local configuration settings can be localized in a web.config file that travels with the application and can be xcopy deployed. Especially if you use the managed module no further configuration beyond copying the web.config file to the server is required as virtuals, scriptmaps and permissions are all set in the .config file.

If you're runing on IIS 7 and you are running your application in a single virtual directory (or the root) using the managed module is highly recommended as it's more stable, slightly more efficient and tuned for IIS 7 and later.

I hope this helps,

+++ Rick ---


Hello.

I recently upgraded from 4.xx to 5.65 and I'm a little confused about which configuration files Web Connection uses and when it uses them. I'm running 5.65, Win2008/IIS7, using ISAPI script-mapping and not the managed handler.

Does WC use the wc.ini file or the web.config file, or both? And what about the myserver.ini file?

Thanks!
Kirk Allen







Rick Strahl
West Wind Technologies


from Maui, Hawaii

Making waves on the Web


Viewing all articles
Browse latest Browse all 10393

Trending Articles