COM component for ASP

[Mike Chaple]

Hi There,

I developed a COM component for ASP that retrieve data for Oracle database. It works fine, however, every time I have to change it, recompile it. When I try to overlay the one old one, it give an error, even after I unregistered it. I have to reboot so it releases it. Then I can copy it over.

Is it possible to overcome this.??

Regards

[techgnome]

Don't reboot.... simply stop the Web Services. UnRegister the DLL, copy the DLL over the old one, and reregister it. Then re-start web services.
It sucks, but it has to do with the way IIS pools threads and connections.

[Mike Chaple]

Thank you for your quick response, however I think I did try that.
I am not sure if I did it in the same sequence, but I will give it a try. I'll let you know..

You are right on the Money about Management.....

Regards

[Mike Chaple]

Well I did try one more time, but does not work, I still have to reboot.

I was wondering if this has to do with the ObjectControl deactivate event ??

Regards

[techgnome]

I don't know..... In my past experice, I found that all I needed to do was stop all web services (web publishing, IIS, everything) then unregister the dll, copy, register, then restart everything...... sound like in your case though, reboot is the only option..

[Mike Chaple]

Can you register the DLL in a server other than where the IIS is running? Is that possible at all ?? I wonder how the DLL can be found??

Would appreciate your input so very much.

Regards

[techgnome]

Originally posted by Mike Chaple
Can you register the DLL in a server other than where the IIS is running? Is that possible at all ?? I wonder how the DLL can be found??

Would appreciate your input so very much.

Regards

Yes, you can do that. I have never personally done, but I know it can. There is a second parameter of CreateObject that you can set to tell it what server to get the object from. But.... I think you'll still have the same problem as IIS will continue to hold the reference.

[Mike Chaple]

Well, I probably misunderstood you, when you say stop the web service, I was stooping IIS form the Admin Console. That does not work for me. Today I decided to stop the IIS Admin Service from SERVICES at the Control Panel. That works for me, not an elegant solution but better than reboot.

I am sure that you relay meant to stop the Service the way I did today.

I want to thank you for all your help.

The direction I am heading is to have a COM component server, so I can unload traffic from the IIS and have a better control over COM Development/Deployment. I am trying to find the Server,createobject parameter that allow me to point to a COM Server in the same Network, but no luck yet.

[techgnome]

Originally posted by Mike Chaple
Well, I probably misunderstood you, when you say stop the web service, I was stooping IIS form the Admin Console. That does not work for me. Today I decided to stop the IIS Admin Service from SERVICES at the Control Panel. That works for me, not an elegant solution but better than reboot.

I am sure that you relay meant to stop the Service the way I did today.

I want to thank you for all your help.

The direction I am heading is to have a COM component server, so I can unload traffic from the IIS and have a better control over COM Development/Deployment. I am trying to find the Server,createobject parameter that allow me to point to a COM Server in the same Network, but no luck yet.

Sorry I wasn't clear either. Yeah, I did mean stopping IIS from the SERVICS screen.
The server parameter works like this:

Set myCOMObj = Server.CreateObject("MyProgID","SomeOtherServerHere")

-- At least that's how I've been lead to believe it works....