Serialization of any data in a single file is quite possible, but you're trying to mix it with UI. Serialization if the data populated in the UI controls is also possible, but this is
absolutely wrong idea which I won't discuss.
Ever heard of separation of concerns?
You have do centralize all this around data, not UI, which can be often changed, replaced, etc. You need to have a separate
data model consisting of pure data classes/structures and use the data model for
both binding with UI and persistence.
For persistence, it's best to use
Data Contract — most robust and non-intrusive approach.
See:
http://msdn.microsoft.com/en-us/library/ms733127.aspx[
^].
See also my past solutions where I advocate this approach and explain its usage in more detail:
How can I utilize XML File streamwriter and reader in my form application?[
^],
Creating a property files...[
^].
Now, as to separation of concerns: you need to isolate UI from both universal and application-specific aspect of your product. You need to get familiar with the following architectural patterns (
http://en.wikipedia.org/wiki/Architectural_pattern[
^]): MVVM, MVC, MVA and MVP.
See my list of them in my past solution:
how to control Controlls of a user interface form through Functions (methods)[
^].
—SA
Submit an article or tip