Terry: Your answer leaves me with even more questions. For instance, I
already use the CMAB in my application to read a 'base' settings file that I
use to supply control settings. These settings come from a server file and
are NOT changed by the user - only myself. As I see it, the CMAB cannot read
anything but the MyApp.exe.config file (i.e. I would want the actual user
preferences settings stored in another XML file such as AppSettings.xml -
and the CMAB cannot be told to 'read' this file instead).
Also, even if I did use the CMAB, are you saying that the best way would be
to manually populate the CMAB? Remember, I am going to use a Property Grid
to interface the settings to the user. Would not simply serializing the
class that I 'bind' to the Property Grid suffice? Or are there bigger issues
to this?
Don't get the wrong idea - I am open to using the CMAB. I just don't see any
way for it to read anything but the base config file, and since I use that
file to supply hard-coded info to my users, I can't use it to store user
preferences. Again, not trying to answer my own question, but just curious
of the various ways I could do this (and what would be the most logical).
Thanks.
Tom
"One Handed Man ( OHM - Terry Burns )" <news.microsoft.com> wrote in message
news:(E-Mail Removed)...
>
http://msdn.microsoft.com/library/de.../html/cmab.asp
>
> --
>
> OHM ( Terry Burns )
> . . . One-Handed-Man . . .
> If U Need My Email ,Ask Me
>
> Time flies when you don't know what you're doing
>
> "Tom" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > I am planning on adding a Preferences form to my application and using
the
> > Property Grid to display the preferences to the user. What do you think
> > would be the best way to save these preferences out to an XML file? Use
> the
> > CAB (Configuration Application Block)? Save the preferences in a class
> > object and serialize them out the the XML file? Write them out directly
to
> > the XML file? Other ways???
> >
> > Just want to get some thoughts together... want a way that is easy and
> > flexible (i.e. can add/remove preferences later on without a lot of
hassle
> > or making the user ditch all their preferences and start over).
> >
> > Thoughts?
> >
> > Tom
> >
> >
> >
>
>