Greg,
you can easily unload the COM Server if you run them as pooled or high isolation applications. You do this by creating virtual directories in IIS and selecting high isolation or pooled. Then when you want to recompile you just have to press the 'Unload' button. Better yet, automate this procedure in a project hook (see the one i created in the downloads section). So to answer your question, no, you don't have to constantly do an iisreset.
Another technique is to place frequently changed application code in an external prg or html template that can just be replaced. These techniques are used in the latest version of ActiveVFP...

>I've re-written some ASP routines into VFP COM objects. Good news is performance is at least 8-10X better. Bad news is that the development cycle of compiling and testing the COM objects is insane.
>
>Right now I basically rotate about 20 projects all with the same PRG containing the COM object class. After making changes to the code I build the COM object then go into the ASP code and change the CREATEOBJECT call to the new COM. At that point when I go to the page to test it, the web server locks up that COM object so the next time I build I use a new project (same code) to create a new COM. That way I don't have to take down the server and wait for the COM to get released from memory so I can rebuild. I don't like however registering 20 COM objects almost all the same just so I can keep working.
>
>If there is ONE thing I would have liked to have seen in VFP 9 would be that building a COM object that is already in use would prompt and say "Remove COM from memory?", you click YES and that's it! But I'm assuming that is not an option.
>
>Any ideas on how to best handle the COM object development cycle? Any ideas on how to hook into VFP build process to automate removing the COM from memory? Seems like that could be a pretty darn useful app!!
>
>Thanks in advance!!!