Bug 2111 - Deleting/replacing values from an enum declaration does not delete them from the DOM
Summary: Deleting/replacing values from an enum declaration does not delete them from ...
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: Trunk
Hardware: PC Mac OS
: High normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2011-11-21 05:49 UTC by Alan McGovern
Modified: 2011-12-29 06:44 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Alan McGovern 2011-11-21 05:49:38 UTC
I had weird issues where removing members from an enum did not remove them from the DOM so I'd end up with 20 members in the autocomplete list even though my actual enum only had 7.
Comment 1 Mike Krüger 2011-11-25 06:30:06 UTC
I assume it's in the newresolver branch ?
Comment 2 Alan McGovern 2011-11-28 05:59:26 UTC
Yes, this was newresolver. It's hard to reproduce though. I'm not sure what sequence triggered the bug.
Comment 3 Mike Krüger 2011-12-06 09:43:34 UTC
Fixed by the type system update.
Comment 4 Atin 2011-12-29 06:44:06 UTC
Please provide the valuable information or steps to reproduce this issue.