I have to ask.
"Only last week, I learned how to get COM objects out of memory so you can recompile them (without restarting the whole web server)." Oh go on, do tell, the suspense is too much.
In IIS there's an UNLOAD in the application section of the properties tab of each virtual directory.
For a moment there you had my hopes up. It only works for an out-of-process component. I suppose I'll have to stick with renaming the component each time to avoid down time.
Not sure if it is relevant in this case, but I often find that killing the dllhost.exe process owned by IWAM_<machine_name> to be a good way of clearing stuff out of memory. Can't claim it's fool-proof, but it is worth trying before a reboot.
>>Can't claim it's fool-proof, but it is worth trying before a reboot<<
Cool. Single button press.
The only SAFE way to make IIS release a DLL is to use the unload feature within IIS. This only works if the application is configured to run out-of-process. The only safe work around which does not require stopping inetinfo.exe which I have found is to use a new name for the component.Does anyone know an alternative?
.NET does automagically make this problem disappear. "Hey customer, you know the project with the ridiculous schedule, why don't we stop and port it to .NET?" I wish it were an option. It's almost Christmas, I deserve a new toy.
Fog Creek Home