FIX: Run-time Macro Errors Cause Developer Studio to Crash

After receiving a run-time exception from a macro, a fatal error message appears and Developer Studio shuts down.

A code bug attempts to delete a run-time exception object twice.

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This bug was corrected in Visual Studio 6.0 Service Pack 3. For more information about Visual Studio service packs, please see the following articles in the Microsoft Knowledge Base:

194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why  (http://support.microsoft.com/kb/194022/EN-US/ )

194295 HOWTO: Tell That Visual Studio 6.0 Service Packs Are Installed  (http://support.microsoft.com/kb/194295/EN-US/ )

Steps to Reproduce Behavior

First save and close all projects and files. Then create a macro that will generate a run-time exception as follows:

1. On the Tools menu, click Macro.
2. In the Macro dialog box, type TestMacro in the Macro Name edit box.
3. Click Edit.
4. When the Add Macro dialog box appears, click OK.
5. The current .dsm macro file opens. The cursor is positioned in the body of the TestMacro procedure. Type ActiveProject = 1 there.
6. On the File menu, click Save.

To execute the macro:

1. On the Tools menu, click Macro. A message might appear asking if you want to reload macros. Click Yes.
2. Select TestMacro in the Macro Name list, and click Run.
3. A macro exception appears. Click No.
4. Repeat steps one through four until a fatal error occurs.