Messages
Reply
Edit
Delete
Take a look in the help file - it talks about how script maps work.
Basically you can simply set up a scriptmap to .wc, then change all your wc.dll links to wc.wc. Everything should still work as it did before then.
But ideally you'll want to take advantage of the way scriptmaps work which is it maps to a Process class and the script name maps the method (ie. Helloworld.wwd where wwd routes to the process class (wwdemo in this case)).
+++ Rick ---
I've never used script maps in Wconnect... does the wc.wc map to a proc or function in my project? like http://somesite.com/myprocname.wc?wiredweb~&etc=etc ?
No - the .NET Handler cannot be directly accessed. It requires a script map such as wc.wc. You would basically have to change all links to wc.wc...
+++ Rick ---
If I want to use the .NET Handler instead of ISAPI.dll can I still use WC.DLL? or do I need to use WebConnectionModule.dll ?
So I would have to change every URL that has wc.dll in it to WebConnectionModule.dll
http://telecom.shieldswired.us/wiredweb/wc.dll?wiredwebx~ to http://telecom.shieldswired.us/wiredweb/WebConnectionModule.dll?wiredwebx~ ?
Thanks
Jim
West Wind Technologies
Making waves on the Web
