Forums

by Wilfred Verkley >> Thu, 9 Mar 2000 6:15:02 GMT

Im debugging a DLL that my Jade application uses for external function calls.

Whenever I change & replace it, i need to unload the jade environment, so that Jade releases its lock on the DLL. Is there a way to force jade to unload the DLL without closing jade itself?

Thanks,

Wilfred.

by Craig Shearer >> Thu, 9 Mar 2000 9:52:13 GMT

I agree, this is really annoying. I would have thought that when you finish running a JADE application that JADE could/should release the external libraries that it used. Not sure whether this is technically possible though.

Craig.

by Frank Pitt >> Mon, 3 Apr 2000 3:38:29 GMT

I agree, this is really annoying. I would have thought that when you finish running a JADE application that JADE could/should release the external libraries that it used. Not sure whether this is technically possible though.

It's technically possible, there's a Microsoft tool that lets you do it "by hand".

You need to explicitly load the DLL using LoadLibrary (process.h from memory), and then explicitly call FreeLibrary when you're finished with it.
Of course it will only unload the DLL if there are no other processes using it.

Frankie