FIX: Visual Studio 2005 may exit unexpectedly when you import a generic type in a Visual Basic 2005 application, and an interface member may be reimplemented incorrectly when you compile a Visual Basic 2005 application

In Visual Studio 2005, you may experience the following problems.

Problem 1

When you import a generic type in a Visual Basic 2005 application, Visual Studio 2005 may exit unexpectedly (crash). Additionally, you may receive the following error message:

Problem 2

Under some special conditions, an interface member may be reimplemented incorrectly when you recompile a Visual Basic 2005 application.

Service pack information

To resolve this problem, obtain the latest service pack for Visual Studio 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

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:

Prerequisites

You must have the Microsoft .NET Framework 2.0 and Visual Studio 2005 installed to apply this hotfix.

Restart requirement

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

Hotfix replacement information

This hotfix replaces the hotfixes that are described in the following Microsoft Knowledge Base articles:

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 the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

If you have Visual Studio 2005 SP1 installed, you do not have to change the registry.

If you do not have Visual Studio 2005 SP1 installed, you must add and then enable the OptimizePDB registry entry to obtain the improved performance that this hotfix provides. To add the OptimizePDB registry entry, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then right-click the following registry key:
   HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\VB Editor
   Note If you use Microsoft Visual Basic 2005 Express Edition, locate and then right-click the following registry key:
   HKEY_CURRENT_USER\Software\Microsoft\VBExpress\8.0\VB Editor
3. 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 entry, follow these steps:

1. In Visual Studio 2005, start the Visual Basic application.
2. On the Build menu, click Clean Solution.

Note The OptimizePDB registry entry improves the Visual Basic 2005 compiler. Therefore, the Visual Basic 2005 compiler can optimize the .pdb file. However, the new .pdb file format is not fully compatible with the old .pdb file format. Additionally, Visual Studio 2005 SP1 always uses the new .pdb file format. Therefore, a version of Visual Studio 2005 that does not have this hotfix applied or that does not have Visual Studio 2005 SP1 installed may be unable to recognize the new .pdb file format. To resolve this problem, use one of the following methods:

• Apply this hotfix on all development computers.
• Install Visual Studio 2005 SP1 on all development computers.
• On the Build menu, click Clean Solution or click Rebuild Solution before you start to debug.

File information

This hotfix package includes the following hotfixes:

• A Visual Studio 2005 hotfix
• A .NET Framework 2.0 hotfix

If you have Visual Studio 2005 SP1 installed, and you are experiencing the symptoms that are described in this article, you must apply only the .NET Framework 2.0 hotfix to update the Visual Basic 2005 command-line compiler.

If you do not have Visual Studio 2005 SP1 installed, and you are experiencing the symptoms that are described in this article, you must apply both these hotfixes.

The English version of this hotfix package 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.

Visual Studio 2005 hotfix, x86-based versions

The .NET Framework 2.0 hotfix, x86-based versions

Visual Studio 2005 hotfix, x64-based versions

The .NET Framework 2.0 hotfix, x64-based versions

Visual Studio 2005 hotfix, Itanium-based versions

The .NET Framework 2.0 hotfix, Itanium-based versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Visual Studio 2005 Service Pack 1.

Steps to reproduce the problem

Problem 1

1. Start Visual Studio 2005.
2. On the File menu, click New Project.
3. Under Project types, click Visual Basic.
4. Under Templates, click Class Library.
5. Type Test for the project name, and then click OK.
6. In the Class1.vb file, replace the existing code with the following code.

   Imports Test.ContainerClass(Of Test.ConcreteClass)
   
   Public Class ErrorVB
   
       Private d As DateTime = DateTime.Now
   
       Public Sub Method1()
           Dim c1 As DateTime = d.Subtract(New TimeSpan(2, 0, 0, 0))
           Dim c2 As DateTime = d.AddDays(2)
   
           Dim x As InnerClass
   
       End Sub
   
       Public Sub Method2()
           Dim d1 As DateTime = d.Subtract(New TimeSpan(2, 0, 0, 0))
           Dim d2 As DateTime = d.AddDays(2)
   
           Dim x As InnerClass
   
       End Sub
   
   End Class
   
   Public Class ContainerClass(Of T)
   
       Public Class InnerClass
   
       End Class
   
   End Class
   
   Public Class ConcreteClass
   
   End Class

Problem 2

1. Start Visual Studio 2005.
2. On the File menu, click New Project.
3. Under Project types, click Visual Basic.
4. Under Templates, click Console Application.
5. Type a project name, and then click OK.
6. In the Module1.vb file, replace the existing code with the following code.

   Module Module1
   
       Sub Main()
           Dim I As I1
   
           I = New C2
           I.A()
   
           I = New C3
           I.A()
       End Sub
   
   End Module
   
   Class C1
       Implements I1
   
   
       Private Sub X() Implements I1.A
           Console.WriteLine("C1's implementation of I1.A")
       End Sub
   
       Private Sub Y() Implements I1.B
           Console.WriteLine("C1's implementation of I1.B")
       End Sub
   
   End Class
   
   Class C2
       Inherits C1
       Implements I1
   
       Overridable Sub A()
           Console.WriteLine("C2.A")
       End Sub
   End Class
   
   Class C3
       Inherits C1
       Implements I1
   
       Private Sub Z() Implements I1.B
           Console.WriteLine("C3's implementation of I1.B")
       End Sub
   
       Overridable Sub A()
           Console.WriteLine("C3.A")
       End Sub
   End Class
   
   Interface I1
       Sub A()
       Sub B()
   End Interface

7. On the Build menu, click Build Solution.

You receive the following result:However, you expect to receive the following result: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: