FIX: The Visual Basic 2005 compiler unexpectedly exits when you work with a Visual Basic 2005-based project in Visual Studio 2005

When you work with a Microsoft Visual Basic 2005-based project in Visual Studio 2005, the compiler unexpectedly exits (crashes). When this problem occurs, you receive one of the following error messages:

Error message 1Error message 2Note This problem is more likely to occur when you work with the following types of projects:

• ASP.NET projects
• Web application projects (WAPs)

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it 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 Product Support Services to obtain the hotfix. For a complete list of Microsoft Product 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.

Prerequisites

You must have Visual Studio 2005 installed to apply this hotfix.

Restart requirement

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

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.

This hotfix includes performance enhancements that are described in the following Microsoft Knowledge Base articles:To obtain improved performance from this hotfix, add and then enable the OptimizePDB registry value. To do this, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry key:
   HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\VB Editor
   Note If you are using Visual Basic Express, the registry key is as follows:
   HKEY_CURRENT_USER\Software\Microsoft\VBExpress\8.0\VB Editor
3. Click Edit, click New, and then click DWORD Value.
4. Type OptimizePDB, and then press ENTER.
5. Right-click OptimizePDB, and then click Modify.
6. Type 1, and then click OK.
7. 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.

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 be unable to read the new .pdb file format. To resolve this issue, use one of the following methods:

• Apply this hotfix on all development computers.
• Click Clean Solution or Rebuild Solution on the Build menu before you start debugging the solution.

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:

• A Visual Studio 2005 package
• A Microsoft .NET Framework 2.0 package

You must install both packages.

Visual Studio 2005 hotfix files

The .NET Framework 2.0 hotfix file

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

For more information, click the following article number to view the article in the Microsoft Knowledge Base: This hotfix also includes the fixes that are described in the following Microsoft Knowledge Base articles: