|
|
You're in the
dotnet general
group:Application Settings Best Way Question
dotnet general:
I'm working on the design stage of a very flexible and parametrized
application. It'll hold about 50 to 60 diferent application settings. Admin users sholud be able to change any application setting to set a new application behavior. I won't use app.config since application will be distributed using click once and settings could change. Settings type are diferent each other, I mean, It could have strings, numeric or image settings. I'll store settings on a Settings table inside a SQL Server Database. I've been asking about the best way to do this and allways get this two options: 1.- Map each setting to a column in the settings table, so I'll have as much colums as application settings. Then create a class in which every property holds an application setting. Each time I need to read an app setting I'll read a class property. That class should contains a GetSettings methid to refresh settings value. 2.- Define a IdSetting, SettingName, SettingValue table that contains each application setting. A new query is completed every time I need to read a setting value. Can anyone point me to the right direction or share his experience doing application settings without confi files? T.I.A. SG
[quoted text, click to view] "Icarus" <gerardomontero@hotmail.com> wrote in message news:%23ITF1VZbIHA.5160@TK2MSFTNGP05.phx.gbl... > I'm working on the design stage of a very flexible and parametrized > application. It'll hold about 50 to 60 diferent application settings. > Admin users sholud be able to change any application setting to set a new > application behavior. > I won't use app.config since application will be distributed using click > once and settings could change. So you don't deploy the app.config in subsequent deployments. [quoted text, click to view] > Settings type are diferent each other, I mean, It could have strings, > numeric or image settings. So, you have one application that's being used by multiple users? [quoted text, click to view] > > I'll store settings on a Settings table inside a SQL Server Database. > > I've been asking about the best way to do this and allways get this two > options: > > 1.- Map each setting to a column in the settings table, so I'll have as > much colums as application settings. Then create a class in which every > property holds an application setting. Each time I need to read an app > setting I'll read a class property. That class should contains a > GetSettings methid to refresh settings value. > > 2.- Define a IdSetting, SettingName, SettingValue table that contains each > application setting. A new query is completed every time I need to read a > setting value. > > Can anyone point me to the right direction or share his experience doing > application settings without confi files? Is this the only use for the SQL Server table is this app setting and nothing else in the application is using SQL Server? What version of the .Net framework is being used?
I'm doing this using an XML file that is read into (and saved from) a
Dictionary<string, string>. You could as easily store it in SQLServer; that would be overkill for us. We have about 50 settings that we are storing. I created a class that I called ConfigManager that handles the updates, deletes, etc. This is a static class that is in its own project, and is called by the rest of the application, with methods like GetValue, Update (which saves the dictionary to disk), Delete (which saves the dictionary), etc. Upon application startup, it checks to see if the file has been created, and if not, it creates it. We have a bunch of hardcoded defaults, and then it reads in whatever else is in the file, into the dictionary. The XML file is being stored in a folder named by our company name, under Environment.SpecialFolder.LocalApplicationData. It is different for every user. We deploy our application via ClickOnce. Since this file is not part of the deployment, and not in the deployment folders, it is retained throughout the updates. So if you want to update the file, you have to write code to do that in the application. I haven't had to do that yet. We don't use the application settings because of the issue with the updates, and because we wanted finer control. RobinS. GoldMail, Inc. ---------------------------- [quoted text, click to view] "Icarus" <gerardomontero@hotmail.com> wrote in message
news:%23ITF1VZbIHA.5160@TK2MSFTNGP05.phx.gbl... > I'm working on the design stage of a very flexible and parametrized > application. It'll hold about 50 to 60 diferent application settings. > Admin users sholud be able to change any application setting to set a new > application behavior. > I won't use app.config since application will be distributed using click > once and settings could change. > Settings type are diferent each other, I mean, It could have strings, > numeric or image settings. > > I'll store settings on a Settings table inside a SQL Server Database. > > I've been asking about the best way to do this and allways get this two > options: > > 1.- Map each setting to a column in the settings table, so I'll have as > much colums as application settings. Then create a class in which every > property holds an application setting. Each time I need to read an app > setting I'll read a class property. That class should contains a > GetSettings methid to refresh settings value. > > 2.- Define a IdSetting, SettingName, SettingValue table that contains each > application setting. A new query is completed every time I need to read a > setting value. > > Can anyone point me to the right direction or share his experience doing > application settings without confi files? > > T.I.A. > > SG >
Thanks for the info RobinS. :)
"RobinS" <robins@imnottelling.com> escribió en el mensaje news:-72dnZOE5rzuPC_anZ2dnUVZ_sytnZ2d@comcast.com... [quoted text, click to view] > I'm doing this using an XML file that is read into (and saved from) a > Dictionary<string, string>. You could as easily store it in SQLServer; > that would be overkill for us. We have about 50 settings that we are > storing. > > I created a class that I called ConfigManager that handles the updates, > deletes, etc. This is a static class that is in its own project, and is > called by the rest of the application, with methods like GetValue, Update > (which saves the dictionary to disk), Delete (which saves the dictionary), > etc. > > Upon application startup, it checks to see if the file has been created, > and if not, it creates it. We have a bunch of hardcoded defaults, and then > it reads in whatever else is in the file, into the dictionary. > > The XML file is being stored in a folder named by our company name, under > Environment.SpecialFolder.LocalApplicationData. It is different for every > user. > > We deploy our application via ClickOnce. Since this file is not part of > the deployment, and not in the deployment folders, it is retained > throughout the updates. So if you want to update the file, you have to > write code to do that in the application. I haven't had to do that yet. > > We don't use the application settings because of the issue with the > updates, and because we wanted finer control. > > RobinS. > GoldMail, Inc. > ---------------------------- > "Icarus" <gerardomontero@hotmail.com> wrote in message > news:%23ITF1VZbIHA.5160@TK2MSFTNGP05.phx.gbl... >> I'm working on the design stage of a very flexible and parametrized >> application. It'll hold about 50 to 60 diferent application settings. >> Admin users sholud be able to change any application setting to set a new >> application behavior. >> I won't use app.config since application will be distributed using click >> once and settings could change. >> Settings type are diferent each other, I mean, It could have strings, >> numeric or image settings. >> >> I'll store settings on a Settings table inside a SQL Server Database. >> >> I've been asking about the best way to do this and allways get this two >> options: >> >> 1.- Map each setting to a column in the settings table, so I'll have as >> much colums as application settings. Then create a class in which every >> property holds an application setting. Each time I need to read an app >> setting I'll read a class property. That class should contains a >> GetSettings methid to refresh settings value. >> >> 2.- Define a IdSetting, SettingName, SettingValue table that contains >> each application setting. A new query is completed every time I need to >> read a setting value. >> >> Can anyone point me to the right direction or share his experience doing >> application settings without confi files? >> >> T.I.A. >> >> SG >> >
"Mr. Arnold" <MR. Arnold@Arnold.com> escribió en el mensaje news:uLamy1ebIHA.5892@TK2MSFTNGP06.phx.gbl... [quoted text, click to view] > Yes> "Icarus" <gerardomontero@hotmail.com> wrote in message > news:%23ITF1VZbIHA.5160@TK2MSFTNGP05.phx.gbl... >> I'm working on the design stage of a very flexible and parametrized >> application. It'll hold about 50 to 60 diferent application settings. >> Admin users sholud be able to change any application setting to set a new >> application behavior. >> I won't use app.config since application will be distributed using click >> once and settings could change. > > So you don't deploy the app.config in subsequent deployments. > >> Settings type are diferent each other, I mean, It could have strings, >> numeric or image settings. > > So, you have one application that's being used by multiple users? [quoted text, click to view] > The app uses SQL Server for data storage.>> >> I'll store settings on a Settings table inside a SQL Server Database. >> >> I've been asking about the best way to do this and allways get this two >> options: >> >> 1.- Map each setting to a column in the settings table, so I'll have as >> much colums as application settings. Then create a class in which every >> property holds an application setting. Each time I need to read an app >> setting I'll read a class property. That class should contains a >> GetSettings methid to refresh settings value. >> >> 2.- Define a IdSetting, SettingName, SettingValue table that contains >> each application setting. A new query is completed every time I need to >> read a setting value. >> >> Can anyone point me to the right direction or share his experience doing >> application settings without confi files? > > Is this the only use for the SQL Server table is this app setting and > nothing else in the application is using SQL Server? > [quoted text, click to view] > What version of the .Net framework is being used? 2.0 >
[quoted text, click to view] "Icarus" <gerardomontero@hotmail.com> wrote in message news:%23gRmg$lbIHA.4712@TK2MSFTNGP04.phx.gbl... > > "Mr. Arnold" <MR. Arnold@Arnold.com> escribió en el mensaje > news:uLamy1ebIHA.5892@TK2MSFTNGP06.phx.gbl... >> >> "Icarus" <gerardomontero@hotmail.com> wrote in message >> news:%23ITF1VZbIHA.5160@TK2MSFTNGP05.phx.gbl... >>> I'm working on the design stage of a very flexible and parametrized >>> application. It'll hold about 50 to 60 diferent application settings. >>> Admin users sholud be able to change any application setting to set a >>> new application behavior. >>> I won't use app.config since application will be distributed using click >>> once and settings could change. >> >> So you don't deploy the app.config in subsequent deployments. >> >>> Settings type are diferent each other, I mean, It could have strings, >>> numeric or image settings. >> >> So, you have one application that's being used by multiple users? > Yes > >> >>> >>> I'll store settings on a Settings table inside a SQL Server Database. >>> >>> I've been asking about the best way to do this and allways get this two >>> options: >>> >>> 1.- Map each setting to a column in the settings table, so I'll have as >>> much colums as application settings. Then create a class in which every >>> property holds an application setting. Each time I need to read an app >>> setting I'll read a class property. That class should contains a >>> GetSettings methid to refresh settings value. >>> >>> 2.- Define a IdSetting, SettingName, SettingValue table that contains >>> each application setting. A new query is completed every time I need to >>> read a setting value. >>> >>> Can anyone point me to the right direction or share his experience doing >>> application settings without confi files? >> >> Is this the only use for the SQL Server table is this app setting and >> nothing else in the application is using SQL Server? >> > The app uses SQL Server for data storage. > >> What version of the .Net framework is being used? >> > 2.0 There is a demo in the .Net 2.0 Application Block Demo, that you can download, about using the app.config that holds configuration information which is pulled into your application as an object. You you can access that object's config data with ease in your application. The app.config demo project also shows one how to use a SystemFileWatch to detect any changes in the programname.app.config during run time to pull the new configuration into the program and use them. It may be something you'll want to look at, as I use it all the time with Windows service and Console applications, where the programname.app.config will have dynamic data in the config used at runtime.
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
| home · blog · groups | Questions? Comments? Contact the dn |