ATL DLL Problem (DLL still in memory)

[IonelBurtan]

I have a question for you guys because there is no dedicated forum for ATL. Maybe you can help.

I have made a ATL DLL project with the Wizards default settings.
I have added an ATL Component of type ActiveX Server Component. I have wrote a dummy method that writes something in the Response Object from ASP called PutSomeResponse(Through the IResponse Interface). It works.
The problem is this:

After I use my component from ASP like this:
<%
Dim obj
Set obj = Server.CreateObject(&quot;MyAspAtl.MyAspComp&quot
Call obj.PutSomeResponse()
Response.Write (&quot;Ceva&quot
Set obj = nothing
%>
The MyAspAtl.Dll is still in memory. Using some tools I have found out that the Dll was loaded by INetInfo.Exe(IIS's Exe), but the reference count for this Dll is 0!!!

So The Dll is not Unloaded.

I need to use the Dll to recompile & stuff.
I have found a workaround like this, but I am not happy with it:
- at command prompt: net stop w3svc
- recompile & stuff
- at command prompt: net start w3svc

Can you tell me what is going on?
Any help greatly appreciated



s-)

Blessed is he who in the name of justice and good will, shepards the week through the valley of darknees...

http://www20.brinkster.com/ionelb

 

[Cagliostro]

In my opinion, the explorer loks the server till shut down. John Fill

ivfmd@mail.md

 

[yoavt]

It is a known problem. The IIS locks the dll in its memeory even though you don't use it anymore. Apperently, the only way to compile is to do what you did - restart the IIS. This action unloads the dll from the IIS's memory. By the way, some times the Visual Interdev locks the dll, after you use the Server.CreateObject method. In this case you have to close the Visual InterDev itself.