FIX: Engine: Collection Not Updated After Removing an Item

 Last reviewed: December 18, 1997
Article ID: Q169333
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

If an item is removed from a unique naming convention collection you can not add an item with the same name on the following call.

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

Normally, a name is associated with a repository object via a naming relationship. The collection for such a relationship provides the scope for the name and can require that all names in the collection be unique. This is the preferred method for naming objects when a given object will be the destination of only one naming relationship.

Steps to Reproduce Problem

  1. Open a repository-based project that uses unique naming.

  2. Remove item "X" from the collection.

  3. Add an item "X" to the same collection.

Expected results:
  • Success.

Actual results:
  • Fails, item already exists. 
Keywords          : VS97FixlistSP2 VS97FixlistSP1 vb5all 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.