AA2e72E said:
I mean "generating a form's layout at runtime and saving the results as
a form class in a .cs file".
I am hoping that, if this is possible, all the properties of controls
(including ones that I may not have explicitly set) will be written to he
CS
file.
Saving the "state" of the form is easy compared to what you want to do...
I think the most intuitive way to accomplish this is to write to a XML or
some other file format immediately before or after every UI modification
statement (new button, change label text, whatever). Basically it will keep
a log of created controls and property changes.
If you keep your XML tag (node) structure _highly_ standardized, you should
be able to quickly parse the data back into a .cs file with some simple yet
elaborate control, iteration, and selection statements.
That's the best I have, but I would love to know how this goes, with
whatever avenue you take. Actually it sounds fun, but I'm playing with
databases today.