Hi,
Is there somewhere on the Internet a description of what a .NET
application config file should contain?
For our application, I have to write passwords encrypted in a config
file. The Enterprise Library does have an encryption method, but that
method doesn't just return a value - no - it wants to write the value
immediately to a config file. Except, it always gives an error, because
no config file contents are ever good enough for it.
The same goes for the ConfigurationMa nager.WriteConf iguration function;
whatever the config file contents, it always seems to give an error. Its
2nd parameter is described as "configValu e: The configuration value to
store", so whatever object you insert there; it always gives an error.
In the book "Profession al C#" Robinson, Cornes, Glynn, etc. describe a
certain config tool, but (1) that tool is completely different in my XP
and (2) it doesn't do what they say it should do.
If Microsoft wants us to use their XML config file concept, then, why,
why, why, don't they properly describe what the contents of such a file
should be and what it should look like.
The whole Developer Environment is stuffed with wizzards, so why isn't
there a "new-configuration-file-with-valid-contents-wizzard"?
Can anyone provide any help?
Joan
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
