How about heavily using configuration variables in web.config?
-
Hi, I am trying to write ASP.NET website that will have many features added to it as time passes, I want to add those features without changing the code, so I plan to use describtion variables in web.config for each added feature, for example: feature: name="FeatureName" RegexFormat=@"\d+", etc.. Options: displayAds = "false", logErrors = "true", etc. The question is: 1. Does loading variables from web.config file take much more time than embedding variables in the code? if so, does this time consuming task happen only when loading the variable for the 1st time and then it is cached in memory, or does it take much time everytime the variable is loaded? and what's the best way to implement such variables that are likely to change, but not in the near future? 2. How does the efficiency compare to storing these variables in a database instead of web.config. P.S.: Those variables will be used heavily in the program. Thanks alot
And ever has it been that love knows not its own depth until the hour of separation Mohammad Gdeisat