"Werner B. Strydom" <bloudraak@hotmail.com> wrote in message
news:O3zysIDREHA.2876@TK2MSFTNGP09.phx.gbl...
> Hi,
>
> I'm having some trouble launching an MFC application from a .NET
> application. In a Winforms application [written in C#], I use the Process
> class to start an MFC application. The MFC application creates, automates
> and destroys several COM objects (including Microsoft Word) in a
background
> thread. Often we will get that the C# application causes the MFC
application
> deadlock, while the C# application waits for the process to terminate. If
at
> that time, I kill the C# application, the MFC application continues.
>
> It seems to be deadlocking in WaitForSingleObject. Using a C++ managed
> class, I used CreateProcess inside a managed class to spawn the MFC
> application; and that deadlocks too in when WaitForSingleObject is called.
> Again killing the .NET application is the only way to get the MFC
> application to continue.
>
> The only way I managed to fix it, is to use C++ managed code to call the
MFC
> code directly; that is without spawning off any process. However, if the
MFC
> application misbehaves, it does sabotage the managed code.
>
> Do you perhaps have an idea why waiting for a MFC process to quit in C# or
> C++ could cause that MFC process to deadlock? This was done in the .NET
> framework 1.0, and MFC 7.0.
>
> Thanks
> Werner
>
>
>