FIX: You may experience performance issues when you use solutions that contain large Visual Basic projects in Visual Studio 2005
This article has been archived. It is offered "as is" and will no longer be updated.
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.
This problem occurs because of performance issues in the Visual Basic 2005 compiler.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
To download this hotfix from the MSDN Code Gallery, visit the following Microsoft Web site:
Note The MSDN Code Gallery displays the languages for which the hotfix is available. If you do not see your language listed, it is because the Code Gallery resource page is not available for that language.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
PrerequisitesNo prerequisites are required.
Restart requirementYou do not have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix replaces the hotfix that is described in Microsoft Knowledge Base article 915038.
Registry informationImportant This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
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:HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\VB EditorHKEY_CURRENT_USER\Software\Microsoft\VBExpress\8.0\VB Editor.
- 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.
- 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.
File informationThe 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.
Visual Studio 2005 package
|File name||File version||File size||Date||Time|
The .NET Framework 2.0 package
|File name||File version||File size||Date||Time|
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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 2005For 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 updatesThis 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
- 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.
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.
Article ID: 917452 - Last Review: 01/16/2015 01:48:18 - Revision: 3.0
- kbnosurvey kbarchive kbfix kbbug kbqfe KB917452