What we have
We have some comprehensive control winforms. To save its state, we use some kind of custom serialized class. Let's say we serialize it in xml. Now we could save this xml as a file in the user directory or include it in some other file ....
But...
Question
if a user creates several of these controls in his winform application (during development), which unique identifier is better to use to find out which saved configuration belongs to which of these controls?
So this identifier should:
- Stay on top of all application launches
- Automatically set (or already set, as we can assume that Control.Name always exists)
- Unique application
I think one could imagine several ways to do this, and I believe that there may be some default methods.
Which is better to use? Why?
source share