We developed an application that uses Excel interop libraries (Microsoft.Office.Interop.Excel) to read some Excel files.
When a problem occur in the application, the event Application.ThreadException is handled, so the resources are released (Excel is closed...).
The problem is that when we use the VS debugger, if we stop the execution (because the process breaks on an exception, or a breakpoint, there are lots of reasons why we'd do that), the resources are not released and Excel stays opened.
And of course, next time the application is launched... it crashes because there are locks on the file.
So I'm looking for a way to force the release of the Excel objects, even when stopped with the debugger.
Any suggestion ?
See Question&Answers more detail:
os 与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…