How does static objects behave in ASP.NET

[Michael]

Hi,

I have a class with static fields. The values of those fields appear to
stick between Web requests. That behaviour is a bit of a surprise to me, as
I would expect the object to be completely destroyed between Web requests
(maybe not technically correct way of describing this, since the fields are
static, there is no object instantiation).

The static fields values do not seem to be shared between sessions though;
that's good.

Any additional info, or pointers to where I can read more about this on the
Net would be much welcomed.

Thanks.

[Stefan]

Uhm, why would a static field be destroyed? It is created when the
_type_ (not an object/instance of this type) is loaded and destroyed.

Also, they will be shared between session (they are similar to
application scoped variables), so I think you should retest that.

[Scott Allen]

I have a few articles on the topic:
You'll find those statics fields are shared across sessions, in fact
each web application will have only one instance of each static field,
so you have to be very careful how you use them in a web app.

I have a few articles on the topic:

Get a Charge From Statics with Seven Essential Programming Tips
http://msdn.microsoft.com/msdnmag/is...T/default.aspx

Statics & Thread Safety: Part I
http://odetocode.com/Articles/313.aspx

Statics & Thread Safety: Part II
http://odetocode.com/Articles/314.aspx

--
Scott
http://www.OdeToCode.com/blogs/scott/
On Wed, 3 Aug 2005 13:56:37 -0700, "Michael" <no****@nospam.com>
wrote:

Hi,

I have a class with static fields. The values of those fields appear to
stick between Web requests. That behaviour is a bit of a surprise to me, as
I would expect the object to be completely destroyed between Web requests
(maybe not technically correct way of describing this, since the fields are
static, there is no object instantiation).

The static fields values do not seem to be shared between sessions though;
that's good.

Any additional info, or pointers to where I can read more about this on the
Net would be much welcomed.

Thanks.

[Michael]

Thanks Stefan.
"Stefan" <Cl*********@gmail.com> wrote in message
news:11**********************@o13g2000cwo.googlegr oups.com...

Uhm, why would a static field be destroyed? It is created when the
_type_ (not an object/instance of this type) is loaded and destroyed.

Also, they will be shared between session (they are similar to
application scoped variables), so I think you should retest that.

[Michael]

Thanks for the info and links.
"Scott Allen" <sc***@nospam.odetocode.com> wrote in message
news:f9********************************@4ax.com...

I have a few articles on the topic:
You'll find those statics fields are shared across sessions, in fact
each web application will have only one instance of each static field,
so you have to be very careful how you use them in a web app.

I have a few articles on the topic:

Get a Charge From Statics with Seven Essential Programming Tips
http://msdn.microsoft.com/msdnmag/is...T/default.aspx

Statics & Thread Safety: Part I
http://odetocode.com/Articles/313.aspx

Statics & Thread Safety: Part II
http://odetocode.com/Articles/314.aspx

--
Scott
http://www.OdeToCode.com/blogs/scott/
On Wed, 3 Aug 2005 13:56:37 -0700, "Michael" <no****@nospam.com>
wrote:

Hi,

I have a class with static fields. The values of those fields appear to
stick between Web requests. That behaviour is a bit of a surprise to me,
as
I would expect the object to be completely destroyed between Web requests
(maybe not technically correct way of describing this, since the fields
are
static, there is no object instantiation).

The static fields values do not seem to be shared between sessions though;
that's good.

Any additional info, or pointers to where I can read more about this on
the
Net would be much welcomed.

Thanks.