Hello:
I'm trying to emulate the userSettings storage system on CE.
XmlSerialization looks like a very useful 1-line solution that looks
wonderful for serializing one class to one xml document -- but not an xml
string fragment...
Because that user.config often has more than just class serialized into
(such as one per assembly if each assembly has a Settings.settings file). An
example would be this:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<!--
Some Notes I want to keep , etc.
-->
<userSettings>
<XAct.Study.UserSettings.Properties.Settings>
<setting name="MyUserSetting2" serializeAs="String">
<value>PinkAndFlufyXTRA</value>
</setting>
<setting name="MyUserSetting" serializeAs="String">
<value>PinkAndFlufy</value>
</setting>
</XAct.Study.UserSettings.Properties.Settings>
<XAct.Module1.Properties.Settings>
<setting name="MoreSettings" serializeAs="String">
<value>Chiwawa</value>
</setting>
<setting name="MoreSettings2" serializeAs="String">
<value>HighPitchedBark</value>
</setting>
</XAct.Module1.Properties.Settings>
</userSettings>
</configuration>
How can I force the XmlSerializer to return everything minus the leading
<?xml version="1.0" encoding="utf-8"?up front, so that I can stringbuild
several classes together before saving it?
BTW: I see one overload that allows for multiple types to be given, but I
don't think that's what I want -- because user.settings may contain other
fragments, notes, etc, so I don't want to give over to the XmlSerializer
complete control of the file (it will erase the notes, etc.).
Or is there a better approach to this?
Thank you very much,
Sky
it appears to create a full xml document, rather than just a string fragment.