"Mark Rae" <ma**@markN-O-S-P-A-M.co.uk> wrote in message
news:ug**************@TK2MSFTNGP09.phx.gbl...
I haven't had a chance to check whether this is fixed in v2 - does anyone
know?
I can confirm that this has *not* been fixed in ASP.NET v2
Here's how to reproduce it.
1) Create a simple web page with an <asp:DropDownList> and an <asp:Button>
2) Create a SelectedIndexChanged method for the DropDownList and a Command
event for the Button
3) Add any single line of code to each event - just enough so you can set a
breakpoint
4) Populate the DropDownList in the Page_Init method - only a couple of
items will do, just enough to cause the event to fire.
5) Set a breakpoint in the SelectedIndexChanged method and the Command
method
6) Run the page in Debug mode
7) Select a different item in the DropDownList - you jump into its
SelectedIndexChanged method as expected - hit F5 to resume
8) Click the Button - you jump into the DropDownList's SelectedIndexChanged
method before jumping into the Button's Command method - that's bad, at
least, to my way of thinking. I would have expected the Page_Init to fire,
the Page_Load to fire and the Button's Command method to fire. I would have
expected the ViewState to remember the DropDownList's selection, but not its
SelectedIndexChanged method to fire.
Can anyone please confirm that this is a bug?