When you use Microsoft Visual Studio 2005 on a system that has an updated version of the Microsoft .NET Framework 2.0 installed, you cannot run a macro in the Visual Studio Macros IDE. When this problem occurs, you do not receive an error message, and the macro does not run.
The problem is caused by a recent design change to the common language runtime (CLR) components for the .NET Framework 2.0. This change may cause compatibility issues for the design-time engine of Microsoft Visual Studio for Applications. Visual Studio 2005 uses the design-time engine of Visual Studio for Applications for macro capabilities. These compatibility issues may prevent the macro script from being compiled successfully or from being loaded successfully. Therefore, the macro does not run.
Service pack information
To resolve this problem, obtain the latest service pack for Visual Studio 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest Visual Studio 2005 service pack
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Visual Studio 2005 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note
In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Visual Studio 2005 Service Pack 1.
For more information about a similar problem in the Visual Studio for Applications runtime engine, click the following article number to view the article in the Microsoft Knowledge Base:
FIX: Custom applications that use the Visual Studio for Applications Visual Basic Runtime may be unable to compile macros or to run macros
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
Description of the standard terminology that is used to describe Microsoft software updates