I have a very old webconnect application (5.53 running on Server 2008, I think) using a .abc scriptmap pointing to its related path to wc.dll

Now I need to add more functionality (and overwrite some functions) without rewriting the existing app - the app has code handling in too many modules to be a quick change.

I presume it's not as simple as using a new handler for scriptmap ".abcd" pointing to a different wc.dll and executable in order to add new or overwritten functionality using the same domains...

I assume there might be conflicts between the old wc.dll and the current webconnect wc.dll - if I remember correctly, I suspect all my instances will use the first loaded wc.dll.

If all that is correct, perhaps I need to create a new subdomain to handle the new functionality... at least in the short term. A rewrite of the whole application is out of the question right now...

Perhaps I can create a subdomain on another server to handle overridden functions, but I might have to pass the info back to the Win2008 in some cases.

Thoughts?

The DLL -> EXE mapping via COM is 1 to 1. So if you're running in COM mode you can't have multiple EXEs off the same DLL. Hoever, you can have multiple scriptmaps that point at the same EXE and then have the new code run in that same EXE.

If you're running in File Mode you have more options, as you can point each script map to a different temp folder, and each of those temp folders could potentially be served by different EXEs via their configuration pointing at the appropriate temp folders/prefixed files.

+++ Rick ---

Interesting approach... Would it work if I kept the existing site in COM mode and created a second site working in FILE mode - serving a different extension - on the same Win2008 server?

Would that require a different domain name in the URL?

Perhaps I can create a subdomain on another server to handle overridden functions, but I might have to pass the info back to the Win2008 in some cases.

If you plan on having two executables (old and new) you could create a second site and application pool in IIS, and point it to do a different port than the first (e.g. use 8080 instead of 80), then make a subdomain that points to the new port.

We build an EXE for VFP data and another one for SQL Server, and can host them on the same server this way, both running in COM mode. (We're using .NET Handler on WWWC8, so I can't say for sure that would work for you.)

If you use separate sites, you can use COM too and just map the handler to a separate EXE.

The key is that each Com can only be mapped to a single DLL within an individual site, but with multiple sites each site can map to its own Com server.