Tim Mackey's Weblog

... unless you DataBind() the LoginView first of all.  just posting this in case i forget!

this wasn't very obvious to work out, and i couldn't find a decent solution online, so i came up with this.

this.DropDownList1.Attributes.Add("onchange", "if(!confirm('Are you sure you want to delete this item?')) return;");

This works with .Net 2 and 3 and 3.5, but may break with future versions if .Net changes the javascript code for AutoPostBack drop down lists.  The reason it works now is because .Net adds the custom 'onchange' attribute before it's on doPostBack() function call.  So if we return from the confirm prompt, the form will not submit. 

great post by Curtis Keisler explaining how to do this: http://www.devblog.com/2007/12/update-all-fields-in-word-document.html

I was in the same boat as a lot of the folks on this MSDN forum thread.  Vista stability went out the window a few weeks ago.  mostly related to Search, but disabling the Search service only seemed to shift the problems to explorer.exe or lsass.exe.  installing SP1 RC1 refresh 2 seeemed to help but after rebuilding the index the same problems came back.  i found some useful info about lsass, and finally found a great solution by Aaron Tiensivu on his blog post about resetting a corrupt vista user profile. i didn't think it had anything to do with a corrupt profile, but the stuck-in-a-loop lsass.exe activity referencing the SamSs service made me try it out.  it did work, but after a day or two the explorer.exe CPU problems came back.  however, disabling Search has given me normal stability back, which is very welcome.  it's running smoothly so far. 

i guess Windows 7 isn't that far away really, hopefully MS will be more careful next time :)