Microsoft KB Archive/835455

= The Macros IDE does not save changes automatically when you close it in Visual Studio .NET or Visual Studio 2005 =

Article ID: 835455

Article Last Modified on 11/27/2007

-

APPLIES TO


 * Microsoft Visual Studio .NET 2003 Professional Edition
 * Microsoft Visual Studio .NET 2003 Enterprise Architect
 * Microsoft Visual Studio .NET 2003 Enterprise Developer
 * Microsoft Visual Studio .NET 2003 Academic Edition
 * Microsoft Visual Studio .NET 2002 Professional Edition
 * Microsoft Visual Studio .NET 2002 Enterprise Architect
 * Microsoft Visual Studio .NET 2002 Enterprise Developer
 * Microsoft Visual Studio .NET 2002 Academic Edition
 * Microsoft Visual Studio 2005 Professional Edition
 * Microsoft Visual Studio 2005 Standard Edition

-





SYMPTOMS
In Microsoft Visual Studio .NET or Microsoft Visual Studio 2005, you use the Macros IDE to make changes to a macro. However, when you close the Macros IDE, it does not save the changes automatically and you do not receive a prompt to save the changes. Therefore, the changes are not saved.



WORKAROUND
To work around this behavior, save the changes that you have made to your macro before you close the Macros IDE.



STATUS
This behavior is by design.



Steps to reproduce the behavior
 Start Visual Studio .NET or Visual Studio 2005. On the Tools menu, point to Macros, and then click Macro Explorer. In Macro Explorer, right-click MyMacros, and then click New module. The Add Module dialog box appears. In Name box, type TestModule, and then click Open. In Macro Explorer, right-click TestModule, and then click Edit. The Macros IDE starts.  Add a function to the TestModule module as follows: Imports EnvDTE Imports System.Diagnostics

Public Module TestModule

Function Sample ' Sample code End Function

End Module </li> On the File menu, click Close and Return.

Do not save the changes that you have made to the macro.</li></ol>

Note When you close the Visual Studio .NET or Visual Studio 2005 IDE, you receive a prompt to save the changes that you have made to your macro projects. However, if Visual Studio .NET or Visual Studio 2005 quits unexpectedly (crashes) or stops responding (hangs), you may not be able to save the changes. You may also lose track of saved changes because Visual Studio .NET or Visual Studio 2005 does not prompt you to save the changes if you open a new project or if you close the current project without quitting Visual Studio .NET or Visual Studio 2005.

<div class="references_section">