"David B. Bitton" <david@codenoevil.com> wrote in message
news:uZ7t4UHVEHA.4064@TK2MSFTNGP11.phx.gbl...
> It appears as if System.Configuration.ConfigXmlDocument does not handle
> whitespace properly. This stems from an issue I am having with
> deserializing an XmlNode (which is actually a ConfigXmlElement). If I
> compare the InnerXml to a regular XmlElement, things such as newline's and
> tabs (\r\n and \t) they are absent, but if you look at the InnerXml for a
> ConfigXmlElement, they are there.
>
> Unfortunately, the presense of these extra control characters throws off
the
> XmlSerializer because if you look at the dynamically generated code used
for
> (de)serialization, it doesn't know how to handle a whitespace or
> siginificant whitespace element.
>
> It appears if we have two defects here. One is with the ConfigXmlDocument
> and the other is with the XmlSerializer. Hopefully they will be addressed
> soon.
>
> --
> --
>
> David B. Bitton
> david@codenoevil.com
> www.codenoevil.com
>
> Code Made Fresh DailyT
>
>

"Dennis Redfield" <dennis.redfield@acadia-ins.com> wrote in message
news:O3etj04VEHA.3988@tk2msftngp13.phx.gbl...
> now I am really lost. MSDN:
> The ConfigXmlDocument type supports the .NET Framework infrastructure and
is
> not intended to be used directly from your code.
>
> so what's up David.
>
>
>
> dlr
>
> "David B. Bitton" <david@codenoevil.com> wrote in message
> news:uZ7t4UHVEHA.4064@TK2MSFTNGP11.phx.gbl...
> > It appears as if System.Configuration.ConfigXmlDocument does not handle
> > whitespace properly. This stems from an issue I am having with
> > deserializing an XmlNode (which is actually a ConfigXmlElement). If I
> > compare the InnerXml to a regular XmlElement, things such as newline's
and
> > tabs (\r\n and \t) they are absent, but if you look at the InnerXml for
a
> > ConfigXmlElement, they are there.
> >
> > Unfortunately, the presense of these extra control characters throws off
> the
> > XmlSerializer because if you look at the dynamically generated code used
> for
> > (de)serialization, it doesn't know how to handle a whitespace or
> > siginificant whitespace element.
> >
> > It appears if we have two defects here. One is with the
ConfigXmlDocument
> > and the other is with the XmlSerializer. Hopefully they will be
addressed
> > soon.
> >
> > --
> > --
> >
> > David B. Bitton
> > david@codenoevil.com
> > www.codenoevil.com
> >
> > Code Made Fresh DailyT
> >
> >
>
>