BUG: IntelliSense feature of Visual Studio .NET 2003 does not work correctly when you use the VBCommenter add-in in a solution that includes a report project (842434)



The information in this article applies to:

  • Microsoft SQL Server 2000 Reporting Services

Bug #: 161612 (SQL Server 8.0)
SQL BU Defect Tracking:161612

SYMPTOMS

After you build a solution that has a Microsoft Visual Basic .NET project, such as a console application, in Microsoft Visual Studio .NET 2003, the IntelliSense feature in Visual Studio .NET 2003 does not work correctly. This problem may occur if all the following conditions are true:
  • A report project is added to the solution that already has a Visual Basic .NET project.
  • The VBCommenter add-in tool for Visual Studio .NET 2003 is installed on your computer, and the VBCommenter options are enabled.
Note This problem may occur in projects other than Visual Basic .NET projects, such as Microsoft Visual C# projects, that use IntelliSense.

WORKAROUND

To work around this problem, close the solution, restart Visual Studio .NET 2003, and then reopen the solution. To do this, follow these steps:
  1. Close the Visual Studio .NET 2003 solution.
  2. Quit Visual Studio .NET 2003.
  3. Start Visual Studio .NET 2003.
  4. Open your Visual Studio .NET 2003 solution.
Note After you reopen the solution, IntelliSense works correctly. However, if you rebuild the solution, the problem that is mentioned in the "Symptoms" section may occur again.

STATUS

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

MORE INFORMATION

VBCommenter is a third party add-in tool that is designed for Visual Studio .NET 2003. When you turn on the VBCommenter options, the VBCommenter automatically includes the XML comments in the Visual Basic source code.

Although the VBCommenter add-in tool is designed to work with the Visual Basic source code, if you turn on the VBCommenter options for a solution that contains a project other than a Visual Basic project that uses IntelliSense, and you add a report project to your solution, the problem in the "Symptoms" section may occur.

Steps to reproduce the problem

  1. Install the VBCommenter add-in tool for Visual Studio .NET 2003 on your computer. To download the VBCommenter add-in tool for Visual Studio .NET 2003, visit the following Web site: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
  2. Start Visual Studio .NET 2003.
  3. On the File menu, point to New, and then click Project.
  4. Under Project Types, click Visual Basic Projects.
  5. Under Templates, click Console Application.
  6. In the Name box, type TestVBproject, and then click OK.
  7. On the Tools menu, click VBCommenter Options.
  8. In the VBCommenter Settings dialog box, click to select the following check boxes, and then click OK:
    • Create .xml files when projects are built
    • Insert XML comments in source
  9. Make sure that IntelliSense is working correctly in Visual Studio .NET. To make sure that IntelliSense works correctly, type the following code in the Visual Basic source code:
    Dim x As<Space character>
    Note IntelliSense lists all the available interfaces and classes in Visual Basic .NET that can be used to complete the statement.
  10. On the File menu, point to Add Project, and then click New Project.
  11. Under Project Types, click Business Intelligence Projects.
  12. Under Templates, click Report Project.
  13. In the Name box, type TestReportProj, and then click OK.
  14. Check to see if IntelliSense works correctly.
  15. On the Build menu, click Build Solution.

    Note After you build the solution, IntelliSense does not work correctly.
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

Modification Type:MajorLast Reviewed:6/22/2004
Keywords:kb3rdparty kbAddIn kbReport kbtshoot kbbug KB842434 kbAudDeveloper