>>You can still do it in the generated code - just move the members' code into their separate class definitions, and just rename their object appearances in the form class code. You may even be very specific and selective about what will remain in the form's class definition, and what will be in the definitions of its members.
>
>Yeah. But it's not automated, though the browser probably makes doing this with cut'n paste fairly easy. I guess I'd be inclined to develop my form and its controls then create a bunch of subclasses by saving each control as a class. Then use your cut'n paste method for subsequent, evolutionary mods.
>
>Not sure how this all fits in with the design-it-first-then-build-it ideal, but when your just learning and need to create on the fly to fight some fires that are burning now, this seems like a reasonable approach.

Quite so - and that's the reason nobody ever made it automated. You don't do it that often to need it automated, you do it few times and next time you have the control classes ready, so this move-source-around method is all you need.