"Robin" <rottsRule@community.nospam> wrote in message
news:6D0A5B87-176B-4305-BC71-11C391A1D292@microsoft.com...
> I'm sure it's something simple I'm overlooking but... I have a .NET app
> written in C#. I imported a couple of different COM servers via the Add
> Reference->COM window. I then start up the servers by "new"ing them up
> (see
> example code below). The server starts up correctly. The problem is that
> when
> my application exits, the server doesn't go away. I.e. if I look at Task
> Manager, I still see the process running - in the case of my example,
> Winword. I thought maybe it just took a couple of minutes for the process
> to
> be released but no matter how long I wait, it doesn't go away and I have
> to
> manually kill the process. Any ideas what I'm doing wrong?
>
> Thanks, Robin
>
> EXAMPLE CODE:
>
> using System;
> using System.Runtime.InteropServices;
> using System.Reflection
> using Word = Microsoft.Office.Interop.Word;
>
> namespace MySpace
> {
> class Driver
> {
> private Word._Application m_word;
>
> internal void startWord()
> {
> m_word = new Word.Application();
> }
> }
> }
>

"Phil Wilson" wrote:

> Marshal.ReleaseComObject might help.
> --
> Phil Wilson
> [Microsoft MVP-Windows Installer]