-
Sorry for the long question, but I want to cover it from all angles.
After doing a resources check, I am very concerned
I have created a simple COM+ object to check my findings.
The COM+ object was built in VB6 and has one class module. The class module has one function:
Public Function ReturnSomething()
ReturnSomething = "This is from COM+"
End Function
I created myapp.dll and registered it in 'Component Services'
I have called the COM+ object from my asp page using:
Set MyCom = Server.CreateObject("Module.Function")
Response.Write MyCom.ReturnSomething()
Set MyCom = Nothing
As soon as the asp page has loaded, it has returned the string from the COM+ object, but looking through task manager, dllhost.exe appears, and chews up nearly 2mb of resources. I have read that components should terminate automatically after the server has processed the page, but this does not seem to be true.
On my original asp page, I am calling three different COM+ objects which generates three big dllhost.exe entries in the resource viewer.
I am running the COM+ object on Windows 2000 Advanced Server.
Can you force the COM+ object or dllhost.exe to close after the page has finished processing or have I missed something. I have checked a lot of examples and most of them don't even : Set MyCom = Nothing. Please Help!!
-
Nope, this should be fine. I've always used the regsvr control - never done this any other way.
If you need help, look at this thread :
http://forums.vb-world.net/showthrea...light=register
Look at this thread to see if the Dll register worked :
http://forums.vb-world.net/showthrea...light=register
-
Thanks, but whats the advantage of using 'Component Services' in Windows 2000 :confused:
