FIX: You may experience performance issues in the IDE after you use Visual Studio 2008 to build a Visual Basic project

Consider the following scenario:

You use Microsoft Visual Studio 2008 to build a Microsoft Visual Basic project.
The Visual Basic project contains many XML comments in a single file.
The file is probably a designer-generated file for a dataset or for a Web reference.

In this scenario, you may experience the following performance issues in the IDE:

The IDE takes a long time to build the solution and to rebuild the solution.
You experience a slow response time when you press F5 to start debugging.
You experience a slow response time in the Code Editor.
You experience a slow response time in IntelliSense.



This problem occurs because of how the Visual Studio 2008 compiler processes large files that contain XML documentation.



Download information

The following file is available for download from the Microsoft Download Center:
DownloadDownload the 338762_ENU_i386_zip.exe package now. (


Hotfix information

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 2008 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.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

File name File version File size Date Time
Avvspkdh.dll 9.0.21022.43 34,816 29-Jan-2008 03:17
Mcee.dll 9.0.21022.43 367,608 29-Jan-2008 03:17
Mpishim.exe 9.0.21022.43 26,112 29-Jan-2008 03:17
Msvb7.dll 9.0.21022.43 4,069,880 29-Jan-2008 03:17
Msvsmon.exe 9.0.21022.43 3,004,416 29-Jan-2008 03:17



To work around this problem, use one of the following methods.


Method 1: Disable XML comment generation

To disable XML comment generation for the project, use one of the following procedures.

Visual Studio 2008

1. In Solution Explorer, right-click ProjectName, and then click Properties.
2. On the Compile tab, click to clear the Generate XML documentation file check box.
3. On the File menu, click Save All.

Visual Basic 2008 Express Edition

1. Create a backup of the project.
2. In Notepad, open the .vbproj file for the project.
3. Locate and then delete all the <DocumentationFile> elements in the .vbproj file.

Note Typically, you will delete two elements in the .vbproj file.


Method 2: Remove the XML comments

To remove the XML comments, follow these steps for the designer-generated file:

1. On the Edit menu, point to Find and Replace, and then click Quick Replace.
2. In the Find what box, type ”’.
3. In the Replace with box, type , and then click Replace All.

Note You must repeat these steps if you perform one of the following actions:

You save the designer file that generated this code file.
You refresh the Web reference.
You right-click the file, and then you click Run Custom Tool.


Method 3: Create a separate project to store the file that has the XML comments

Create a new class library project to store the designer-generated files. The following procedure is an example of to do this:

1. Create a new class library project to store files that contain a dataset or that contain a Web reference.
2. In the original Visual Basic project, add a reference to the new class library project.
3. Use Method 1 to disable the XML documentation file.

Note You may have to add import statements to the Visual Basic code.



Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.



Feedback.aspx?kbNumber=824684/) Description of the standard terminology that is used to describe Microsoft software updates

For more information about how to generate XML documentation for a project, visit the following Microsoft Developer Network (MSDN) Web site: (

Microsoft Visual Studio 2008 Professional Edition
Microsoft Visual Studio 2008 Academic Edition
Microsoft Visual Studio 2008 Standard Edition
Microsoft Visual Basic 2008 Express Edition
Microsoft Visual Studio Team System 2008 Team Suite
Microsoft Visual Studio Team System 2008 Database Edition
Microsoft Visual Studio Team System 2008 Architecture Edition
Microsoft Visual Studio Team System 2008 Development Edition
Microsoft Visual Studio Team System 2008 Test Edition


Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

AddThis Social Bookmark Button

Leave a Reply

To prove that you're not a bot, enter this code
Anti-Spam Image