You may receive an error message when you try to open a .vb file in Visual Studio 2005, in Visual Studio .NET 2003, or in Visual Studio .NET 2002

Symptoms

When you try to open a .vb file in Microsoft Visual Studio 2005, in Microsoft Visual Studio .NET 2003, or in Microsoft Visual Studio .NET 2002, you may experience one of the following symptoms.

Visual Studio 2005

You receive the following error message:
Microsoft (R) Visual Basic Compiler has encountered a problem and needs to close. We are sorry for the inconvenience.



No information has been lost. Check the compiler output for possible ways to avoid this error.
If you click What data does this error report contain?, you receive the following Event information:Additionally, events that resemble the following are logged in the Application log:
Event message 1
Event message 2

Visual Studio .NET 2003 or Visual Studio .NET 2002

You receive the following error message:
Microsoft Developement Environment has encountered a problem and needs to close. We are sorry of the inconvenience.
If you click Click here, you receive the following Event information:Additionally, an event that resembles the following may be logged in the Application log:

Cause

This problem occurs because the Visual Basic runtime installation has become corrupted.

Resolution

To resolve this problem, repair or reinstall Visual Studio. To do this, use one of the following methods, depending on the version of Visual Studio that you have installed.

Visual Studio 2005

  1. Insert the Visual Studio 2005 installation CD.
  2. Click Change or Remove Visual Studio 2005.
  3. Click Next, and then click Repair/Reinstall to start the installation.
  4. When the installation has completed, click Finish.

Visual Studio .NET 2003 or Visual Studio .NET 2002

  1. Insert the Visual Studio .NET 2003 or Visual Studio .NET 2002 installation CD.
  2. Click Visual Studio .NET.
  3. Click Repair/Reinstall to start the installation.
  4. When the installation has completed, click Finish.

Status

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

ID do Artigo: 919482 - Última Revisão: 13 de mai de 2008 - Revisão: 1

Comentários