Sanity Check
-
ASP.NET 2.0 is also stateless in that static variables in the page behind will not maintain their value between page loads correct?
// TODO: Write code.
-
ASP.NET 2.0 is also stateless in that static variables in the page behind will not maintain their value between page loads correct?
// TODO: Write code.
Sorry, didn't see the 2.0 in the question. This applies to 1.0 and 1.1, but I would think that it would be a huge breaking change to change this behavior in 2.0. Static variables are maintained until the AppDomain is recycled. If you use static variables in ASP.Net they need to be protected with locks. In most cases, an application level variable is a better choice for static type data. Also, if you need something at a request level of granualarity, the context has an items collection.