Microsoft KB Archive/917452

= FIX: You may experience performance issues when you use solutions that contain large Visual Basic projects in Visual Studio 2005 =

Article ID: 917452

Article Last Modified on 12/6/2006

-

APPLIES TO


 * Microsoft Visual Basic 2005
 * Microsoft Visual Studio 2005 Professional Edition
 * Microsoft Visual Studio 2005 Standard Edition

-



Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
When you develop a Microsoft Visual Basic solution that contains large projects in Microsoft Visual Studio 2005, you may experience the following performance issues in the Visual Studio 2005 IDE:
 * It takes longer to build and to rebuild the solution.
 * You experience a slow response time when you press F5 to start debugging.
 * You experience a slow response time when you perform symbolic renaming. CPU utilization may increase to more than 50 percent during the renaming process.
 * You experience slow response time in the Code Editor.
 * You experience slow response time in IntelliSense.
 * Virtual memory consumption by Visual Studio 2005 is increased compared with earlier versions of Visual Studio.



CAUSE
This problem occurs because of performance issues in the Visual Basic 2005 compiler.



Hotfix information
A supported hotfix is now available from Microsoft. But the hotfix is intended only to correct the problem that is described in this article. Apply this hotfix 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, visit the following Microsoft Web site:

http://go.microsoft.com/fwlink/?LinkID=76565&clcid=0x409

Prerequisites
No prerequisites are required.

Restart requirement
You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information
This hotfix replaces the hotfix that is described in Microsoft Knowledge Base article 915038.

Registry information
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To obtain more performance gain from this hotfix, add the OptimizePDB registry value. To do this, follow these steps:  Click Start, click Run, type regedit, and then click OK. Locate and then click the following registry key:

 

Note If you are using Visual Basic Express, the registry key should be the following:  . Click Edit, click New, and then click DWORD Value. Type OptimizePDB, and then press ENTER. Right-click OptimizePDB, and then click Modify. Type 1, and then click OK.</li> Exit Registry Editor.

After you add the OptimizePDB registry value, open the Visual Basic solution in Visual Studio 2005. Then, click Clean Solution on the Build menu.</li></ol>

The OptimizePDB registry value makes the Visual Basic compiler optimize the .pdb file to improve performance. However, the new .pdb file format is not fully compatible with the old .pdb file format. Therefore, a version of Visual Studio 2005 that does not have this hotfix applied may not be able to read the new format of the .pdb file. To resolve this issue, apply this hotfix on all development computers, or click Clean Solution or Rebuild Solution on the Build menu before debugging.

File information
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.

This hotfix includes two packages. One package is for Visual Studio 2005, and one package is for the Microsoft .NET Framework 2.0. Tell the Microsoft Support Professional the package that you want.

The .NET Framework 2.0 package
<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

MORE INFORMATION
This performance hotfix has been merged with the hotfix that is described in Microsoft Knowledge Base article 915038. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

915038 FIX: You may receive Visual Basic compiler error messages when you are developing a Visual Basic 2005 project in Visual Studio 2005

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

This performance hotfix affects the following areas of Visual Basic 2005:
 * Compilation throughput
 * Symbolic rename performance
 * Build performance
 * Memory consumption that is caused by XML documentation and by overhead from the Edit and Continue feature

When you apply this hotfix, you experience the following performance improvements in Visual Studio 2005:
 * You experience a faster build and rebuild response time.
 * You experience a faster response time when you press F5 to start debugging.
 * You experience faster renaming of user controls in the Designer and Code views.
 * You experience a reduced time for IntelliSense to appear in the editor.
 * You experience a reduced time to interact with the code editor.
 * You experience reduced virtual memory consumption by the Devenv.exe process.
 * When you modify code or you rename controls, you experience reduced CPU utilization in both severity and duration.

If you install this hotfix and you do not have the Msxml6.dll file installed on the computer for some reason, you may receive the following error message for your XML comment blocks:

Warning 1 XML documentation parse error: An invalid character was found in text content. XML comment will be ignored.

To resolve this problem, install the MSXML 6.0 Parser that is included on the Visual Studio 2005 installation media.

Keywords: kbfix kbbug kbhotfixserver kbqfe KB917452

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.