Problem with COM server

[Olivier Paumier]

Hi,

we have an application with a COM interface (developped in VC++ 6),
and one of our customers is currently creating with VB.net a client
for this application.
The problem is that after the client calls our server application, if
the server application is then closed using the usual GUI way, the
window is closed, the application is now more listed in the task
manager (application tab), but the process remains.
There was no such problem when using a VB6 client.

Do you see what could cause such a behaviour ?

Thanks in advance.

Olivier Paumier

[Jayson Knight]

Hello Olivier,

System.Runtime.InteropServices.Marshal.ReleaseComO bject(package);

Hi,

we have an application with a COM interface (developped in VC++ 6),
and one of our customers is currently creating with VB.net a client
for this application.
The problem is that after the client calls our server application, if
the server application is then closed using the usual GUI way, the
window is closed, the application is now more listed in the task
manager (application tab), but the process remains.
There was no such problem when using a VB6 client.
Do you see what could cause such a behaviour ?

Thanks in advance.

Olivier Paumier

[Olivier Paumier]

Jayson Knight <ja********@carolina.rr.com> wrote in message news:<eR**************@TK2MSFTNGP12.phx.gbl>...

Hello Olivier,

System.Runtime.InteropServices.Marshal.ReleaseComO bject(package);

Hello Jayson,

thanks for your advice. The hint you gave me is to release the RCW
once you're done with the COM server, isn't it ?
Now there's still a problem remaining for me, in the case the COM
server was closed by the user and not by the .net client, how can the
..net client be aware of it ?
Our COM application does not send any "quit" event, is it necessary or
is there a way to do it without it ?

Thanks in advance.

Cheers,

Olivier

[Olivier Paumier]

Jayson Knight <ja********@carolina.rr.com> wrote in message news:<eR**************@TK2MSFTNGP12.phx.gbl>...

Hello Olivier,

System.Runtime.InteropServices.Marshal.ReleaseComO bject(package);

Hello Jayson,

thanks for your advice. The hint you gave me is to release the RCW
once you're done with the COM server, isn't it ?
Now there's still a problem remaining for me, in the case the COM
server was closed by the user and not by the .net client, how can the
..net client be aware of it ?
Our COM application does not send any "quit" event, is it necessary or
is there a way to do it without it ?

Thanks in advance.

Cheers,

Olivier