>So, is there a way to re-register the executable without rerunning setup?
/regserver
You may also have to reset the DComCnfg settings and you have to kill hte server.
As John pointed out, IIS is pretty stupid about updating binaries and will not let you replace anythinhg that's in use. Web Connection has a mechanism to dynamically unload all running servers, swap in a new binary, then reload everything. This assumes the EXE file's classIDs and type library haven't changed, which is fine with WC (there's only 1 OLEPUBLIC method which never changes). But if you're using FoxISAPI is highly unlikely because the Interfaces constantly change as you add OLEPUBLIC methods. With FoxISAPI you'll have to reregister your components.
+++ Rick ---
> > >>Forgot to answer the question... You have to kill the IIS session and the fox session, then restart. The program is still in memory. > >> Hi John, > >> I think he'll have to re-register it also as I believe the registry ID's will > change. > >> Bill
