Why have the difference between web.config and app.config

[ad]

When I add a connection string by wizard in a WebApp , the wizard add the
connection string to web.config like
<add name="MyDataBas e" connectionStrin g="Data Source=.\SQLEXP RESS;Initial
Catalog=xxxx;.. ...

But if I add the same connection string by wizard in a class library
project, the connection string in app.config will be:
<add name="dataHealt h.Properties.Se ttings.MyDataBa se"
connectionStrin g="Data Source=.\SLEEPE RS;Initial Catalog=xxxx...

The connection string name in app.config will be initial with
"ProjectName..P roperties.Setti ngs"
Why have the difference between web.config and app.config

[Christopher Reed]

For a web application, you would use web.config. For either an EXE or class
library DLL, you would use the "app".confi g. The difference with the
connection string name is so that you can maintain uniqueness among multiple
config files. Also, the web.config can be accessed from either
System.Configur ation.Configura tionManager or
System.Web.Conf iguration.WebCo nfigurationMana ger.

I'm not sure if this is what you're looking for.
--
Christopher A. Reed
"The oxen are slow, but the earth is patient."

"ad" <fl****@wfes.tc c.edu.tw> wrote in message
news:u$******** ******@TK2MSFTN GP14.phx.gbl...

When I add a connection string by wizard in a WebApp , the wizard add the
connection string to web.config like
<add name="MyDataBas e" connectionStrin g="Data Source=.\SQLEXP RESS;Initial
Catalog=xxxx;.. ...

But if I add the same connection string by wizard in a class library
project, the connection string in app.config will be:
<add name="dataHealt h.Properties.Se ttings.MyDataBa se"
connectionStrin g="Data Source=.\SLEEPE RS;Initial Catalog=xxxx...

The connection string name in app.config will be initial with
"ProjectName..P roperties.Setti ngs"
Why have the difference between web.config and app.config