Article ID: 891516 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
When you debug Microsoft Visual Basic .NET code in the Microsoft Visual Studio .NET 2003 IDE, code that accesses the properties and the methods of the base interface is skipped. The Microsoft intermediate language (MSIL) in the MSIL Disassembler (Ildasm.exe) code shows that the MSIL code is not generated for the corresponding Visual Basic .NET source. You experience this problem when the following two conditions are true:
This problem occurs because Visual Basic .NET does not generate the required code. When Visual Basic .NET assemblies and Microsoft Visual C# assemblies have a single inheritance hierarchy but have duplicate interface names, Visual Basic does not generate code when you access the base interface methods or attributes.
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 .NET 2002 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:
http://support.microsoft.com/contactus/?ws=supportNote 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.
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 tool in Control Panel.
Date Time Version Size File name ----------------------------------------------------- 21-Dec-2004 22:44 7.10.4348.0 598,016 Bcaut.dll 22-Dec-2004 02:35 7.10.4348.0 1,437,696 Msvb7.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Steps to reproduce this problem:
(https://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates