I haven't leveraged ISAPI DLLs in a number of years but I am considering their use in an upcoming project. Has much changed in this arena as far as problems debugging/updating the DLLs? One thing is new - I can more easily create a stand alone application for help with debugging - but what about version updates, is there a pattern for that these days? I was debating on having a proxy DLL up front which decides which version to submit the request to.
Debugging ISAPI DLLs is not hard. Takes 10 minutes to do proper IIS setup and you are done. You can also use other web servers like Abyss which has an excellent ISAPI support and it is simpler to debug using it.
ReplyDeleteAbout the proxy DLL: It is a good option if you really need it. You can create your own (which is not difficult) or you can use something like: eggcentric.com - EGGCentric - ISAPI Tools
ReplyDeleteOn IIS you can replace an in use ISAPI DLL renaming it and copying the new one to the same folder. It works, but the new one will only be used when IIS unloads the old version (after a full IIS restart or an application pool recycle)
Ahh....been a long time since I saw that tool. That page probably hasn't changed in a decade!
ReplyDelete