Appropriate way of dealing with settings in my app?

[Linda]

In classic ASP I used to have a file called settings.asp included on every
page of my web, it consisted of a number of different settings unique to
this application, among them the database path etc.
I used to set some of the values contidional to which server executed the
script (see listing below). This way I could download the files, edit and
test run them locally, then put them back on the production server again
without having to worry about changing the paths each time.

My question now is: What would be the appropriate way of dealing with this
in .net?

/ Linda

-- partial content of settings.asp --

'--- Locally--------------------
If InStr(Request.S erverVariables( "SERVER_NAM E"), "mydevserve r") Then
DBPATH = "DRIVER={Micros oft Access Driver (*.mdb)};
DBQ=D:\inetpub\ wwwroot\custome r\db\survey.mdb ;"
BASE_URL = "http://mydevserver/customer/survey/"
FILE_FOLDER = "/files/"
'--- In production--------------
ElseIf InStr(Request.S erverVariables( "SERVER_NAM E"),
"customerserver .com") Then
DBPATH = "DRIVER={Micros oft Access Driver (*.mdb)};
DBQ=E:\webhotel \customers\cust omerserver.com\ db\survey.mdb;"
BASE_URL = "http://www.customerser ver.com/survey"
FILE_FOLDER = "/virtualfiledir/"
End If

[Scott Allen]

Hi Linda,

Use the app settings section in your web.config file:

<appSettings>
<add key="FileFolder " value="/foo" />
</appSettings>
You can read the settings with a little bit of code:
string fileFolder =
ConfigurationSe ttings.AppSetti ngs["FileFolder "];

And you can pull environment specific settings into an external file
and reference the file from web.config:

<appSettings file="devsettin gs.config"/>

Where devsettings.con fig would contain an <appSettings> element.

http://odetocode.com/Articles/345.aspx

HTH,

--
Scott
http://www.OdeToCode.com/blogs/scott/
On Fri, 18 Mar 2005 16:25:25 +0100, "Linda"
<linda(at)ordin arystar.com> wrote:

In classic ASP I used to have a file called settings.asp included on every
page of my web, it consisted of a number of different settings unique to
this application, among them the database path etc.
I used to set some of the values contidional to which server executed the
script (see listing below). This way I could download the files, edit and
test run them locally, then put them back on the production server again
without having to worry about changing the paths each time.

My question now is: What would be the appropriate way of dealing with this
in .net?

/ Linda

-- partial content of settings.asp --

'--- Locally--------------------
If InStr(Request.S erverVariables( "SERVER_NAM E"), "mydevserve r") Then
DBPATH = "DRIVER={Micros oft Access Driver (*.mdb)};
DBQ=D:\inetpub \wwwroot\custom er\db\survey.md b;"
BASE_URL = "http://mydevserver/customer/survey/"
FILE_FOLDER = "/files/"
'--- In production--------------
ElseIf InStr(Request.S erverVariables( "SERVER_NAM E"),
"customerserve r.com") Then
DBPATH = "DRIVER={Micros oft Access Driver (*.mdb)};
DBQ=E:\webhote l\customers\cus tomerserver.com \db\survey.mdb; "
BASE_URL = "http://www.customerser ver.com/survey"
FILE_FOLDER = "/virtualfiledir/"
End If

[Brock Allen]

In web.config you can use the <appSettings> section to store your custom
application settings (note that it's case sensitive):

<configuratio n>
<appSettings>
<add key="SomeKey" value="SomeValu e" />
</appSettings>
</configuration>

Then in you app:

string val = System.Configur ation.Configura tionSettings.Ap pSettings["SomeKey"];
// use val here....

-Brock
DevelopMentor
http://staff.develop.com/ballen

In classic ASP I used to have a file called settings.asp included on
every
page of my web, it consisted of a number of different settings unique
to
this application, among them the database path etc.
I used to set some of the values contidional to which server executed
the
script (see listing below). This way I could download the files, edit
and
test run them locally, then put them back on the production server
again
without having to worry about changing the paths each time.
My question now is: What would be the appropriate way of dealing with
this in .net?

/ Linda

[Juan T. Llibre]

Set all the constants/properties in a class file which
you compile to an assembly and place in the /bin
directory of your application.

It's easy to call any constant/property from that .dll

Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======

"Linda" <linda(at)ordin arystar.com> wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..

In classic ASP I used to have a file called settings.asp included on every
page of my web, it consisted of a number of different settings unique to
this application, among them the database path etc. I used to set some of the values contidional to which server executed the
script (see listing below). This way I could download the files, edit and
test run them locally, then put them back on the production server again
without having to worry about changing the paths each time.

My question now is: What would be the appropriate way of dealing with this
in .net?

/ Linda -- partial content of settings.asp --

'--- Locally--------------------
If InStr(Request.S erverVariables( "SERVER_NAM E"), "mydevserve r") Then
DBPATH = "DRIVER={Micros oft Access Driver (*.mdb)};
DBQ=D:\inetpub\ wwwroot\custome r\db\survey.mdb ;"
BASE_URL = "http://mydevserver/customer/survey/"
FILE_FOLDER = "/files/"
'--- In production--------------
ElseIf InStr(Request.S erverVariables( "SERVER_NAM E"),
"customerserver .com") Then
DBPATH = "DRIVER={Micros oft Access Driver (*.mdb)};
DBQ=E:\webhotel \customers\cust omerserver.com\ db\survey.mdb;"
BASE_URL = "http://www.customerser ver.com/survey"
FILE_FOLDER = "/virtualfiledir/"
End If

[Linda]

You guys are quick, thanks!!

I have looked briefly into the world of app settings before, and it solves
most of my problem, at least as long as I am the only developer involved.
But at some point there will be other developers, designers etc involved,
who have the bad habit of always downloading/uploading the entire app, of
course resulting in the exact same files in both (or all) locations.
Is there a way to solve that, other than educating my co-workers ;)
Is there a way to force the use of different app setting-files for different
locations. Or maybe it is posible to refer to an app setting file in a
directory outside of the actual application folder, where those co-workers
would never think to look?

/ Linda

"Scott Allen" <sc***@nospam.o detocode.com> wrote in message
news:4q******** *************** *********@4ax.c om...

Hi Linda,

Use the app settings section in your web.config file:

<appSettings>
<add key="FileFolder " value="/foo" />
</appSettings>
You can read the settings with a little bit of code:
string fileFolder =
ConfigurationSe ttings.AppSetti ngs["FileFolder "];

And you can pull environment specific settings into an external file
and reference the file from web.config:

<appSettings file="devsettin gs.config"/>

Where devsettings.con fig would contain an <appSettings> element.

http://odetocode.com/Articles/345.aspx

HTH,

--
Scott
http://www.OdeToCode.com/blogs/scott/
On Fri, 18 Mar 2005 16:25:25 +0100, "Linda"
<linda(at)ordin arystar.com> wrote:

In classic ASP I used to have a file called settings.asp included on everypage of my web, it consisted of a number of different settings unique to
this application, among them the database path etc.
I used to set some of the values contidional to which server executed the
script (see listing below). This way I could download the files, edit and
test run them locally, then put them back on the production server again
without having to worry about changing the paths each time.

My question now is: What would be the appropriate way of dealing with thisin .net?

/ Linda

-- partial content of settings.asp --

'--- Locally--------------------
If InStr(Request.S erverVariables( "SERVER_NAM E"), "mydevserve r") Then
DBPATH = "DRIVER={Micros oft Access Driver (*.mdb)};
DBQ=D:\inetpub \wwwroot\custom er\db\survey.md b;"
BASE_URL = "http://mydevserver/customer/survey/"
FILE_FOLDER = "/files/"
'--- In production--------------
ElseIf InStr(Request.S erverVariables( "SERVER_NAM E"),
"customerserve r.com") Then
DBPATH = "DRIVER={Micros oft Access Driver (*.mdb)};
DBQ=E:\webhote l\customers\cus tomerserver.com \db\survey.mdb; "
BASE_URL = "http://www.customerser ver.com/survey"
FILE_FOLDER = "/virtualfiledir/"
End If

[Brock Allen]

I have a sample of building your own custom configuration sections which
uses the XmlSerializer. This is a very common technique in v1.x:

http://staff.develop.com/ballen/samp...nfigSample.zip

-Brock
DevelopMentor
http://staff.develop.com/ballen

You guys are quick, thanks!!

I have looked briefly into the world of app settings before, and it
solves
most of my problem, at least as long as I am the only developer
involved.
But at some point there will be other developers, designers etc
involved,
who have the bad habit of always downloading/uploading the entire app,
of
course resulting in the exact same files in both (or all) locations.
Is there a way to solve that, other than educating my co-workers ;)
Is there a way to force the use of different app setting-files for
different
locations. Or maybe it is posible to refer to an app setting file in a
directory outside of the actual application folder, where those
co-workers
would never think to look?
/ Linda

"Scott Allen" <sc***@nospam.o detocode.com> wrote in message
news:4q******** *************** *********@4ax.c om...

Hi Linda,

Use the app settings section in your web.config file:

<appSettings>
<add key="FileFolder " value="/foo" />
</appSettings>
You can read the settings with a little bit of code: string
fileFolder = ConfigurationSe ttings.AppSetti ngs["FileFolder "];

And you can pull environment specific settings into an external file
and reference the file from web.config:

<appSettings file="devsettin gs.config"/>

Where devsettings.con fig would contain an <appSettings> element.

http://odetocode.com/Articles/345.aspx

HTH,

--
Scott
http://www.OdeToCode.com/blogs/scott/
On Fri, 18 Mar 2005 16:25:25 +0100, "Linda"
<linda(at)ordin arystar.com> wrote:

In classic ASP I used to have a file called settings.asp included on
every
page of my web, it consisted of a number of different settings
unique to
this application, among them the database path etc.
I used to set some of the values contidional to which server
executed the
script (see listing below). This way I could download the files,
edit and
test run them locally, then put them back on the production server
again
without having to worry about changing the paths each time.
My question now is: What would be the appropriate way of dealing
with
this
in .net?

/ Linda

-- partial content of settings.asp --

'--- Locally--------------------
If InStr(Request.S erverVariables( "SERVER_NAM E"), "mydevserve r") Then
DBPATH = "DRIVER={Micros oft Access Driver (*.mdb)};
DBQ=D:\inetpub\ wwwroot\custome r\db\survey.mdb ;"
BASE_URL = "http://mydevserver/customer/survey/"
FILE_FOLDER = "/files/"
'--- In production--------------
ElseIf InStr(Request.S erverVariables( "SERVER_NAM E"),
"customerserver .com") Then
DBPATH = "DRIVER={Micros oft Access Driver (*.mdb)};
DBQ=E:\webhotel \customers\cust omerserver.com\ db\survey.mdb;"
BASE_URL = "http://www.customerser ver.com/survey"
FILE_FOLDER = "/virtualfiledir/"
End If

[Kevin Spencer]

I agree with both schools of thought (web.config and class). There are uses
for both. For example, you can only store text data in the web.config. You
can store objects in a class. On the other hand, the web.config is read into
memory and remains memory-resident for the life of the app. A class can have
static methods that don't require instantiation, but often will require
instantiation. So, keep in mind what your options are, and use the
appropriate method.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
What You Seek Is What You Get.

"Juan T. Llibre" <no***********@ nowhere.com> wrote in message
news:OV******** ******@TK2MSFTN GP15.phx.gbl...

Set all the constants/properties in a class file which
you compile to an assembly and place in the /bin
directory of your application.

It's easy to call any constant/property from that .dll

Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======

"Linda" <linda(at)ordin arystar.com> wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..

In classic ASP I used to have a file called settings.asp included on
every
page of my web, it consisted of a number of different settings unique to
this application, among them the database path etc.

I used to set some of the values contidional to which server executed the
script (see listing below). This way I could download the files, edit and
test run them locally, then put them back on the production server again
without having to worry about changing the paths each time.

My question now is: What would be the appropriate way of dealing with
this
in .net?

/ Linda

-- partial content of settings.asp --

'--- Locally--------------------
If InStr(Request.S erverVariables( "SERVER_NAM E"), "mydevserve r") Then
DBPATH = "DRIVER={Micros oft Access Driver (*.mdb)};
DBQ=D:\inetpub\ wwwroot\custome r\db\survey.mdb ;"
BASE_URL = "http://mydevserver/customer/survey/"
FILE_FOLDER = "/files/"
'--- In production--------------
ElseIf InStr(Request.S erverVariables( "SERVER_NAM E"),
"customerserver .com") Then
DBPATH = "DRIVER={Micros oft Access Driver (*.mdb)};
DBQ=E:\webhotel \customers\cust omerserver.com\ db\survey.mdb;"
BASE_URL = "http://www.customerser ver.com/survey"
FILE_FOLDER = "/virtualfiledir/"
End If

[JV]

One way might be to encapsulate it into a Web User control. They are easy
to make though they don't have much visual representation at design time.
In your case that's no big deal.

Also, keep in mind that straight ASP techniques generally still work in
ASP.NET. They just might be the "old way" of doing things.

You could perhaps put a script block into each web form. They look
something like:

<script language=C# runat=server>
(code here)
</script>

You might try using the "src" attribute to refer to your asp include file.
I've never tried combining "runat=serv er" with a "src" attribute, but I
imagine it should work.

-jv
"Linda" <linda(at)ordin arystar.com> wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..

In classic ASP I used to have a file called settings.asp included on every
page of my web, it consisted of a number of different settings unique to
this application, among them the database path etc.
I used to set some of the values contidional to which server executed the
script (see listing below). This way I could download the files, edit and
test run them locally, then put them back on the production server again
without having to worry about changing the paths each time.

My question now is: What would be the appropriate way of dealing with this
in .net?

/ Linda

[JV]

Actually, now that I reread your post, I would recommend putting the
settings in your WEB.CONFIG file and using the folllowing collection object
to retrieve them in each page:

System.Configur ation.Configura tionSettings.Ap pSettings

Search for "Introducti on to Dynamic Properties" in the online help for
details.
"Linda" <linda(at)ordin arystar.com> wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..

In classic ASP I used to have a file called settings.asp included on every
page of my web, it consisted of a number of different settings unique to
this application, among them the database path etc.
I used to set some of the values contidional to which server executed the
script (see listing below). This way I could download the files, edit and
test run them locally, then put them back on the production server again
without having to worry about changing the paths each time.

My question now is: What would be the appropriate way of dealing with this
in .net?

/ Linda

-- partial content of settings.asp --

'--- Locally--------------------
If InStr(Request.S erverVariables( "SERVER_NAM E"), "mydevserve r") Then
DBPATH = "DRIVER={Micros oft Access Driver (*.mdb)};
DBQ=D:\inetpub\ wwwroot\custome r\db\survey.mdb ;"
BASE_URL = "http://mydevserver/customer/survey/"
FILE_FOLDER = "/files/"
'--- In production--------------
ElseIf InStr(Request.S erverVariables( "SERVER_NAM E"),
"customerserver .com") Then
DBPATH = "DRIVER={Micros oft Access Driver (*.mdb)};
DBQ=E:\webhotel \customers\cust omerserver.com\ db\survey.mdb;"
BASE_URL = "http://www.customerser ver.com/survey"
FILE_FOLDER = "/virtualfiledir/"
End If

[David Alpert]

A couple of options occur off the top of my head:

a) configure your team's FTP software to ignore "web.config " files
(Dreamweaver does it with "cloaking", NAnt and other tools with
regular expressions of some sort)

b) if your deployments are to known servers with predictable and
stable URLs, you could hard code the settings into an assembly (dll)
with a static accessor that does some sort of switching on the current
URL.

b.1) depending on how complicated your configuration is, you may even
draft an Interface and then derive an actual configuration class for
each deployment.

then again, these 'b' options may result in deploying lots of extra
code with each setup, so a simpler solution, depending on your
toolset, would be 'a'. :-)

David.