This article has been archived. It is offered "as is" and will no longer be updated.
When you use Microsoft Visual Basic .NET 2003 to modify a project or to edit source code, the Task List may display random false compiler errors for code that is known to be valid.
The false compiler errors may disappear if you close and then reopen the Microsoft Visual Studio .NET development environment or if you rebuild the project by clicking Rebuild project name or Rebuild Solution on the Build menu. However, the false compiler errors return later when you make more changes to the project or source code. For example, the following false compiler errors may appear in the Task List:
Name 'property name / method name' is not a member of 'type name'.
Name 'variable name' is not declared.
Type 'type name' is not defined.
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 2003 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.
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 ----------------------------------------------------- 11-Jun-2003 03:30 7.10.3162.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.
A false compiler error is defined as a compile error shown in the Task List, which prevents the build from completing by indicating problems with source code known to be valid.
If you are receiving other symptoms while compiling your solution; such as a hang, abnormal termination of Visual Studio .NET, or a "Visual Basic internal compiler error", this hotfix will not address that symptom. A Visual Basic internal compiler error returns the following message.
Visual Basic .NET compiler is unable to recover from the following error: System Error &Hc0000005& (Visual Basic internal compiler error) Save your work and restart Visual Studio .NET.
For more information about hotfixes available for Visual Basic internal compiler errors, click the following article numbers to view the articles in the Microsoft Knowledge Base:
836154 FIX: "System Error &Hc0000005&" error message when you create a new project by using a custom template in Visual Studio .NET 2003
831489 BUG: The Visual Basic .NET compiler may stop responding when you try to build a project in Visual Studio .NET
819349 BUG: "Visual Basic Internal compiler error" error message occurs when the ADDHANDLER statement or the REMOVEHANDLER statement is used
For more information about the terminology that is used to describe Microsoft product updates, 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 updates