How to release excel process?

Question

I'm using the Excel interop and it seems to be creating a process every time I call

new Microsoft.Office.Interop.Excel.Application()

And never ending the process even though I call

xlApp.Quit();

How can I get the processes to end?

score 3 · Accepted Answer · answered Sep 28 '10 at 14:58

Are you releasing all of your references? (Which means you have to save them in the first place).

For example here's what's in my dispose from some excel interop():

    public void Dispose()
    {
        if(!this.disposed)
        {
            if(cell != null)
                Marshal.FinalReleaseComObject(cell);

            if(cells != null)
                Marshal.FinalReleaseComObject(cells);

            if(worksheet != null)
                Marshal.FinalReleaseComObject(worksheet);

            if(worksheets != null)
                Marshal.FinalReleaseComObject(worksheets);

            if (workbook != null)
            {
                workbook.Close(false, Type.Missing, Type.Missing);
                Marshal.FinalReleaseComObject(workbook);
            }

            Marshal.FinalReleaseComObject(workbooks);
            xlApp.Quit();
            Marshal.FinalReleaseComObject(xlApp);

            GC.Collect();
            GC.WaitForPendingFinalizers();

            disposed = true;
        }
    }

(Not sure if this is perfect but it worked for me!)

My objects were locally scoped, so I put that in a finally, but it works, thanks! — C. Ross, Sep 28 '10 at 14:59

score 1 · Answer 2 · edited May 23 '17 at 12:11

1

Excel won't quit if you don't release used COM Objects.

This Answer should provide more information.

edited May 23 '17 at 12:11

Community

1
1

answered Sep 28 '10 at 14:57

marg

2,817
1
31
34

Yeah, that's where I got my solution from, mainly. Although I found just doing what the chosen answer selected wasn't enough, I had to put the Close(), the Quit() and the GC calls in there too. Difficult to get rid of, those damn Excel spreadsheets! – Grant Crofton Sep 28 '10 at 15:03

score 0 · Answer 3 · answered Sep 28 '10 at 14:58

Most of the time this happens because you did modify the document and Excel is waiting for some saving. Try something like:

ObjWorkBook.Close(Microsoft.Office.Interop.Excel.XlSaveAction.xlDoNotSaveChanges, 
    Type.Missing, Type.Missing);

before quitting

How to release excel process?

3 Answers3

Linked