Writing to App.Config

[Frank Oquendo]

ConfigurationSe ttings.AppSetti ngs allows me to read from my config but how
do I write to my config file?

--
There are 10 kinds of people. Those who understand binary and those who
don't.

http://code.acadx.com
(Pull the pin to reply)

[_]

Frank,

ConfigurationS ettings.AppSett ings allows me to read from my config but how
do I write to my config file?

Download the TFTP Server eval components from www.abderaware.com and look at the
Configuration class (configuration. cs).

Cya! :-)
--
Abderaware
Fine Components For .NET
Turn on, tune in, download.
zane a@t abderaware.com

[Miha Markic [MVP C#]]

Hi Frank,

Writting into .config file is not a good idea.
The config files are intended to give administrators a way to configure
certain settings and not to persist settings.
They reside (normally) under program files folder thus only admin (if not
set otherwise) can edit them.

If you have settings that you need to persist consider storing them in
user-specific or app-specific area.

--
Miha Markic [MVP C#] - RightHand .NET consulting & software development
miha at rthand com
www.rthand.com
"Frank Oquendo" <fr****@acadxpi n.com> wrote in message
news:e1******** ******@TK2MSFTN GP10.phx.gbl...

ConfigurationSe ttings.AppSetti ngs allows me to read from my config but how
do I write to my config file?

[_]

On Tue, 10 Feb 2004 08:41:50 +0100, "Miha Markic [MVP C#]" <miha at rthand com>
wrote:

The config files are intended to give administrators a way to configure
certain settings and not to persist settings.
They reside (normally) under program files folder thus only admin (if not
set otherwise) can edit them.

What supporting documentation do you have for that statement? I don't mean to
be confrontational , I really am curious to know if I missed some position taken
by MS on that point.

--
Abderaware
Fine Components For .NET
Turn on, tune in, download.
zane a@t abderaware.com

[Miha Markic [MVP C#]]

Hi Zane,

What supporting documentation do you have for that statement? I don't mean to be confrontational , I really am curious to know if I missed some position taken by MS on that point.

For instance, config files are placed into (under) program files folder
where only admins have write access by default.
It is generally not a good idea to allow every user to write into program
files folder.
That is also why MS doesn't support writting to config files.
For that purposes there are other folders (for example ApplicationData ,
CommonApplicati onData, LocalApplicatio nData) - some of them support also
roaming - you can find them by looking at
Environment.Spe cialFolder Enumeration .net help topic.

There you'll find also a useful link with more details on special folders:
http://msdn.microsoft.com/library/de...nums/csidl.asp

Sorry, I don't have other better links right now, but AFAIK this is how it
should be.

HTH,
--
Miha Markic [MVP C#] - RightHand .NET consulting & software development
miha at rthand com
www.rthand.com

[_]

Miha,

For instance, config files are placed into (under) program files folder
where only admins have write access by default.
Whether Frank is developing for such a situation is something we don't know.

That is also why MS doesn't support writting to config files.
For that purposes there are other folders (for example ApplicationData ,
CommonApplicat ionData, LocalApplicatio nData) - some of them support also
roaming - you can find them by looking at
Environment.Sp ecialFolder Enumeration .net help topic.
Or, one can simply use a configuration file in the application's directory.
From MSDN:

<q>
The name and location of the application configuration file depend on the
application's host, which can be one of the following:

Executable–host ed application.
The configuration file for an application hosted by the executable host is in
the same directory as the application. The name of the configuration file is the
name of the application with a .config extension. For example, an application
called myApp.exe can be associated with a configuration file called
myApp.exe.confi g.
</q>
ms-help://MS.VSCC/MS.MSDNVS/cpguide/html/cpconapplicatio nconfigurationf iles.htm

Sorry, I don't have other better links right now ...

Well, until you find some better links ... :-)
--
Abderaware
Fine Components For .NET
Turn on, tune in, download.
zane a@t abderaware.com

[John Smith]

What about on installation? I have on several occasions had an installation
class write to the App.Config. I create a DataSet, then read the App.Config
with ReadXml() . The installer class then updates the Data Set and then
calls WriteXml method of the data set.
I would agree that you should avoid using .config files for most things, but
they seem a natural for things you would otherwise use the registry for.
Else why would they have the appSettings section?

"Miha Markic [MVP C#]" <miha at rthand com> wrote in message
news:ux******** ******@TK2MSFTN GP09.phx.gbl...

Hi Frank,

Writting into .config file is not a good idea.
The config files are intended to give administrators a way to configure
certain settings and not to persist settings.
They reside (normally) under program files folder thus only admin (if not
set otherwise) can edit them.

If you have settings that you need to persist consider storing them in
user-specific or app-specific area.

--
Miha Markic [MVP C#] - RightHand .NET consulting & software development
miha at rthand com
www.rthand.com
"Frank Oquendo" <fr****@acadxpi n.com> wrote in message
news:e1******** ******@TK2MSFTN GP10.phx.gbl...

ConfigurationSe ttings.AppSetti ngs allows me to read from my config but how do I write to my config file?

[_]

On Tue, 10 Feb 2004 11:58:18 -0700, "John Smith" <jb****@blackfo ot.com> wrote:

Else why would they have the appSettings section?

Bingo! :-)
--
Abderaware
Fine Components For .NET
Turn on, tune in, download.
zane a@t abderaware.com

[Miha Markic [MVP C#]]

<zane (_) abderaware.com (Zane Thomas)> wrote in message
news:40******** *******@news.mi crosoft.com...

Miha,

For instance, config files are placed into (under) program files folder
where only admins have write access by default.
Whether Frank is developing for such a situation is something we don't

know.

Yes, we don't know. I was talking about common scenarios.

That is also why MS doesn't support writting to config files.
For that purposes there are other folders (for example ApplicationData ,
CommonApplicat ionData, LocalApplicatio nData) - some of them support also
roaming - you can find them by looking at
Environment.Sp ecialFolder Enumeration .net help topic.
Or, one can simply use a configuration file in the application's

directory. From MSDN:

<q>
The name and location of the application configuration file depend on the
application's host, which can be one of the following:

Executable-hosted application.
The configuration file for an application hosted by the executable host is in the same directory as the application. The name of the configuration file is the name of the application with a .config extension. For example, an application called myApp.exe can be associated with a configuration file called
myApp.exe.confi g.
</q>
ms-help://MS.VSCC/MS.MSDNVS/cpguide/html/cpconapplicatio nconfigurationf iles.
htm

Configuration file - not persistent storage file.

Sorry, I don't have other better links right now ...

Well, until you find some better links ... :-)

Do I need them? ;-)

--
Miha Markic [MVP C#] - RightHand .NET consulting & development
miha at rthand com
www.rthand.com

[Miha Markic [MVP C#]]

"John Smith" <jb****@blackfo ot.com> wrote in message
news:uc******** ******@TK2MSFTN GP09.phx.gbl...

What about on installation?
Yes, what about it?

I have on several occasions had an installation class write to the App.Config. I create a DataSet, then read the App.Config with ReadXml() . The installer class then updates the Data Set and then
calls WriteXml method of the data set.
I would agree that you should avoid using .config files for most things, but they seem a natural for things you would otherwise use the registry for.
Else why would they have the appSettings section?

Installation is done under administrator account and have privilege and
right to write into config.
It makes sense to create or modify config file at installation time.
However, they are not intended to be used for storing persistent data from
the application itself, like for example windows position - stuff like that.
Sorry if I was not clear enough on this.

--
Miha Markic [MVP C#] - RightHand .NET consulting & development
miha at rthand com
www.rthand.com