RE: Launch dll and disconnect

Giganews Newsgroups
Subject: RE: Launch dll and disconnect
Posted by:  stche…
Date: Tue, 04 Dec 2007

Hi Jack,

From your description, you have an unmanaged COM based  application which
call a .NET component through COM interop. Currently, you're wondering how
to make the callee .NET component continue running after you terminate the
caller application(unmanaged COM one), correct?

As for this scenario, I'm afraid it is not quite supported if the .NET
component is called through COM interop. Because in such case, the .NET
runtime is hosted in the originoal unmanaged COM based process. If you
terminate it, the whole process end and the CLR runtime also terminate. I'm
not sure whether remote communication is doable in your case, but the
proper way here is host the .NET component in a separate process and
exchange with the unmanagd process through some interprocess communication

Welcome to post here if you have any other concerns here.


Steven Cheng

Microsoft MSDN Online Support Lead


Get notification to my posts through email? Please refer to

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at


This posting is provided "AS IS" with no warranties, and confers no rights.

>From: "Jack" <SonomaJa…@newsgroups.nospam>
>Subject: Launch dll and disconnect
>Date: Mon, 3 Dec 2007 18:22:19 -0600
>I have a COM application that calls a dotNet dll (w/COM Interop enabled)
>kick off a process.  I want to then terminate the originating process and
>have the dotNet dll continue to execute.
>Is there a way to call the dll and have the parent process terminate, then
>have the dll to continue to completion?



In response to

Launch dll and disconnect posted by Jack on Mon, 3 Dec 2007