Static Class VS. Application State

[Smithers]

I have a few variables that need to be accessible throughout my ASP.NET Web
app, across all possible Sessions.

AFAIK, there are two reasonable places to store them:
1. Application state (read the values from Web.config on ApplicationStart()
and then refer to them there).

2. properties of a static class (read values from Web.config when the app
starts, and then refer to them there).

Are there any good reasons to chose one of these approaches over the other?
I have currently implemented via #2, but was just wondering if anyone sees
any problems with that approach.

Thanks!

 

[Robbe Morris [C# MVP]]

#2. Aside from various other reasons, it will allow you to use that same
class in non web environment.

--
2005 Microsoft MVP C#
Robbe Morris
http://www.robbemorris.com
http://www.mastervb.net/home/ng/forumvbcode/post10017013.aspx
http://www.eggheadcafe.com/articles/adonet_source_code_generator.asp

 

[Steve C. Orr [MVP, MCSD]]

#1 is the standard way to do this kind of thing.

#2 isn't necesarrily bad, but you can encounter rare, hard to debug
threading problems if you're not careful about how you implement this.