FIX: Get_Item() Does Not Return Error When Property Not Found

 Last reviewed: December 18, 1997
Article ID: Q169302
The information in this article applies to:
  • Microsoft Visual Studio 97
  • Microsoft Visual Basic Learning, Professional, and Enterprise Editions for Windows, version 5.0

SYMPTOMS

IReposProperties::get_item does not return an error when property is not found.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This has been fixed with Visual Studio Service Pack 1.

For additional information about the Visual Studio 97 Service Pack 1, please see the following article in the Microsoft Knowledge Base: 

   ARTICLE-ID: Q170365
   TITLE     : INFO: Visual Studio 97 Service Packs - What, Where, and Why

MORE INFORMATION

Steps To Reproduce:

  1. Create an interface hierarchy. For example: I1 -> I2 -> I3.

  2. Create a class that implements only Interface 3.

  3. Create an instance of the new class "C."

  4. QI, "QueryInterface", for "C's" Interface 3 Interface.

  5. I->get_Properties(&pIPropCol).

  6. Ask for a property that does not exist on any of the ifaces. For example, pIPropCol->get_Item("Prop1", ....)

Expected result:
  • Should return Property not found error.

Actual result:
  • Returns a Bogus property object containing invalid dispid. 
Keywords          : VS97FixlistSP2 VS97FixlistSP1 VB5FixlistSP2 vb5all VB5FixlistSP1 VS97FixlistSP3
Version           : 5.0 97
Platform          : NT WINDOWS
Issue type        : kbbug
Solution Type     : kbfix kbservicepack

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: December 18, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.