Speaking of ASP.NET feedback, I have a small request that would greatly have simplified my life on a recent project. Of course, I've now had to work around the problem so it may not save me time in the future, but still...

How hard would it be to make Control.NamingContainer writable? Obviously there would have to be some constraints - the value chosen would have to be somewhere in the control's container hierarchy, it would have to be valid as a naming container (ie a repeating block, user control or page - any others?) and you'd have to be careful that you didn't by so doing introduce two controls with the same ID in the same naming container.

In my situation I could trivially have guaranteed all these things, but the framework wouldn't let me do it. I had to instead construct the page one way, extract my viewstate into standalone objects, tear it all down again and build it up again with a new structure, pulling the state from the saved standalone objects - on *every* postback. This was, to put it lightly, a pain in the neck...

Thanks for the feedback Stuart. To make sure all the right people see this you should submit this as a product suggestion here: http://lab.msdn.microsoft.com/productfeedback/