DropDownList ListItem Collection Editor doesn't save changes to aspx source file when DropDownList is inside a container - by T H

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 362593 Comments
Status Closed Workarounds
Type Bug Repros 5
Opened 8/20/2008 12:11:06 AM
Access Restriction Public


At Design Time, adding a DropDownList inside a containing component and then trying to add items to that DropDownList via the ListItems Collection Editor is problematic: Clicking the "OK" button inside the editor closes the editor, but does not update the aspx source file--no items are added to the dropdownlist. It would appear that some update event isn't firing. 

If the DropDownList is not inside of a container, adding items via the list editor works correctly as expected.

I have verified this (what appears to be a) bug on two systems, one with XP SP2 and one with Vista 32 bit. Both VS installations have the recently released VS2008 SP1 installed. I at first thought it was a third party component problem, as I encountered it when placing the DropDown list in an Infragistics UltraWebTab container. But then I also experienced it inside a Telerik RadMultiPage RadPageView component, which led me to try it inside of standard MS container components that come with VS2008 and I found that the problem existed there, too. 

So, I now believe it is a problem with the DropDownList component itself or some base component it is derived from or how the ListItem Collection Editor interacts with it.
Sign in to post a comment.
Posted by UteW on 11/6/2009 at 10:01 AM
So what are we supposed to do until we upgrade to 2010? I think it is really lame to introduce a bug in a service pack and then not offer a fix for it until the next version comes out. Unfortunately, it is another incident of the louse product support we have all come to expect and accept from Microsoft.

Posted by cichanlx on 9/24/2009 at 10:45 AM
So, Microsoft's solution to this bug in 2008 is that it's fixed in 2010? Problem: The brakes on my 2008 car don't work. Solution: It's safe to keep driving it, because the future model will work correctly. Give me a break!
Posted by Microsoft on 2/26/2009 at 9:28 AM

just to let you know that this issue was fixed for Visual Studio 2010
Posted by JCroney on 9/24/2008 at 5:09 AM
This is a regression issue introduced in VS 2008 SP1. It impacts a variety of inbox and custom controls when they are inside of an INamingContainer such as a MultiView, Panel, UpdatePanel, etc. The larger issue here is the lackluster support for nofifying Visual Studio when a property changes from a designer.
Posted by BestCoder3 on 9/11/2008 at 11:44 AM
I see this same thing all the time, on both 32-bit and 64-bit Vista. It seems to occur with just about any control. It isn't just limited to the DropDownList.
Posted by Microsoft on 8/20/2008 at 11:43 PM
Thanks for your feedback. We are escalating this bug to the product unit who works on that specific feature area. The team will review this issue and make a decision on whether they will fix it or not for the next release.

Thank you,
Visual Studio Product Team