Visual Studio : executing clean up code when debugging stops

Question

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 ?

Shay Erlichmen · Accepted Answer · 2009-09-09T06:38:15.323

15

You can use the DTE (VisualStudio Automation Model) to write a macro that will be invoked when a stop debug happens, below is a snippet of the idea.

Private Sub DebuggerEvents_OnEnterBreakMode(
   ByVal Reason As EnvDTE.dbgEventReason, 
   ByRef ExecutionAction As EnvDTE.dbgExecutionAction) Handles DebuggerEvents.OnEnterBreakMode
    If (Reason = dbgEventReason.dbgEventReasonStopDebugging) Then
        // DO YOUR CLEAN UP CODE HERE
    End If
End Sub

edited Sep 09 '09 at 06:38

answered Jun 23 '09 at 15:59

Shay Erlichmen

31,099
7
64
86

3

So sad, no macros in VS 2012+. – roufamatic Feb 25 '14 at 20:18

Simon P Stevens · Answer 2 · 2009-06-24T07:49:23.223

Unfortunately there isn't a way to do this. The stop button in visual studio kills the process, so it doesn't have any chance to clean up.

As a possible way round your problem (although not a very good one), you could write a cleanup routine and execute it manually from the immediate window before stopping the app.

[Edit: Ignore me. This answer is wrong. Shay Erlichmen has come up with a much better solution using a macro]

score 1 · Answer 3 · answered Jun 23 '09 at 18:13

1

One possibility is to switch to a pure .NET solution such as SpreadsheetGear for .NET to get away from the performance and reliability problems associated with COM interop.

Disclaimer: I own SpreadsheetGear LLC

answered Jun 23 '09 at 18:13

Joe Erickson

6,836
1
29
31

Would be nice but a little expensive as we just need to read an excel file :). I looked into open source solutions (like Koogra http://koogra.sourceforge.net/) but it doesn't work with our XLS files. – Julien N Jun 25 '09 at 13:04

Visual Studio : executing clean up code when debugging stops

3 Answers3

Linked