if i have a standard ASP.NET application, is there any difference between making an object static as opposed to putting the object instance in the Application state?
from my understanding, both objects exist ONCE for the app domain.
Secondly, what happens if you have a static object in a referenced dll, for an ASP.NET site. It’s also part of the app domain, so it will always exist once?
Answers:
Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.
Method 1
From: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q312607
ASP.NET includes application state
primarily for compatibility with
classic ASP so that it is easier to
migrate existing applications to
ASP.NET. It is recommended that you
store data in static members of the
application class instead of in the
Application object. This increases
performance because you can access a
static variable faster than you can
access an item in the Application
dictionary.
Also, yes, static variables behave the same way regardless of where they are loaded from, and exist exactly once per app domain (unless you’re talking about those labeled [ThreadStatic])
All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0