Groups | Blog | Home
all groups > dotnet component services > november 2005 >

dotnet component services : Die-hard COM Processes



Phil Galey
11/17/2005 11:33:24 AM
I have a VB.NET application that instantiates a COM object from a DLL using
New(). As the application is closing, it sets the object to Nothing and
does a GC.Collect, but the process does not get removed from memory. It
remains running and listed in Task Manager.

Even if I create a process object using GetProcessesByName and then close or
kill the process, it still persists and GetProcessesByName still finds that
process running.

Does .NET have a "bigger hammer" for bidding fairwell to stubborn processes
like this one? Thanks.

Phil Galey
11/21/2005 8:34:50 AM
Problem solved by powering down completely.


[quoted text, click to view]

AddThis Social Bookmark Button