FIX: Engine: Collection Not Updated After Removing an Item (169333)


The information in this article applies to:

  • Microsoft Visual Studio 97
  • Microsoft Visual Basic Learning Edition for Windows 5.0
  • Microsoft Visual Basic Professional Edition for Windows 5.0
  • Microsoft Visual Basic Enterprise Edition for Windows 5.0
This article was previously published under Q169333

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:

170365 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.
Modification Type:MajorLast Reviewed:1/13/2001
Keywords:kbbug kbVS97sp1fix kbVS97sp2fix KB169333
©2002 Microsoft Corporation. All rights reserved.