Whitespace in app.config

[Steve James]

Has anyone noticed that the xml in an app.config file is treated differently
than in a web.confg, or is it just me?

I have a component that parses and processes node fragments that are taken
from a .config file. When used in a .NET web app ( web.config ) the
component works fine. However, I found when using the identical node
fragment in a Windows app ( app.config ), I got an error. Basically, the
app.config xml had preserved all the whitespace nodes whereas the web.config
version had stripped them all out. Obviously, the solution is to change my
component so it can cope with either scenario, but I find it strange that
the xml is processed differently in each case.

Is this a feature others have come across, or have I done something idiotic?

Steve James

[Dave Bartle]

"Steve James" <st***********@ntlworld.com> wrote in message news:<u4***************@newsfep1-gui.server.ntli.net>...

Has anyone noticed that the xml in an app.config file is treated differently
than in a web.confg, or is it just me?

I have a component that parses and processes node fragments that are taken
from a .config file. When used in a .NET web app ( web.config ) the
component works fine. However, I found when using the identical node
fragment in a Windows app ( app.config ), I got an error. Basically, the
app.config xml had preserved all the whitespace nodes whereas the web.config
version had stripped them all out. Obviously, the solution is to change my
component so it can cope with either scenario, but I find it strange that
the xml is processed differently in each case.

Is this a feature others have come across, or have I done something idiotic?

Steve James

I'm seeing the exact same behavior. If I run the same code in VS.Net
2002 with the 1.0 framework then there's no problem. However in
VS.NET 2003 in my configuration sections all of the whitespace is
preserved (in my case, \r\n\t...). ConfigurationSettings.AppSettings
still seems to work fine.