Re: static class confirmation
- From: "Ignacio Machin \( .NET/ C# MVP \)" <ignacio.machin AT dot.state.fl.us>
- Date: Wed, 15 Mar 2006 08:52:31 -0500
Hi,
"scott blood" <scott_blood@xxxxxxxxxxx> wrote in message
news:uzqabWCSGHA.6084@xxxxxxxxxxxxxxxxxxxxxxx
I think your right there, i just tried this on one of our IIS servers and
the same behaviour appeared.
Beware of this kind of tests, you can get just circumstantials results.
I think because the connection string is not changing asp.net is
intellegent enough not to need to recreate the class for multiple users.
Not at all ! it has nothing to do with "I guess" it has all to do with the
way static are created.
If you actually change the ConnectionString property and then push this
out to your live server, all users on your server will actually be forced
to refresh there current session and all there Session variables are
cleared.
No really, well it does has that effect but not for that reason. When you
change either your web.config or any dll (or even any file) inside your bin
directory the app is recycled. This has the consequence that all the
sessions are lost.
--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation
.
- References:
- static class confirmation
- From: Steven Blair
- Re: static class confirmation
- From: scott blood
- static class confirmation
- Prev by Date: Express Question
- Next by Date: Re: ascii char set
- Previous by thread: Re: static class confirmation
- Next by thread: Re: static class confirmation
- Index(es):
Relevant Pages
|