R
robin9876
After an object is declared, how long will that object be available
until it time's out?
until it time's out?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
M
Mark Rae
After an object is declared, how long will that object be available
until it time's out?
What "object" are you talking about exactly...?
P
Patrice
Not sure what you meant ? Generally speaking an object doesn't timeout.
An ASP.NET session last 20 minutes by default if this is what you meant.
What is the particular problem you have ?
An ASP.NET session last 20 minutes by default if this is what you meant.
What is the particular problem you have ?
A
Aidy
After an object is declared, how long will that object be available
It is available until all references on it are released (at a basic level).
until it time's out?
It is available until all references on it are released (at a basic level).
B
bruce barker
objects are available as long as there is a reference (or the
application exists). asp.net pages are class instances that are create
at start of request, and released at end of request.
-- bruce (sqlwork.com)
application exists). asp.net pages are class instances that are create
at start of request, and released at end of request.
-- bruce (sqlwork.com)
S
Steve C. Orr [MCSD, MVP, CSM, ASP Insider]
Generally objects exist only while they are in scope. After that you can no
longer rely on it being around since the garbage collector will eventually
come around and clean it up (whenever it gets around to it.)
Generally an object created in ASP.NET only lives for milliseconds while the
related page is being rendered on the server. If you need an object to live
a long time then you might consider creating a windows service with which
ASP.NET can interact.
Here's more info on windows services:
http://msdn2.microsoft.com/en-us/library/aa983650(VS.71).aspx
longer rely on it being around since the garbage collector will eventually
come around and clean it up (whenever it gets around to it.)
Generally an object created in ASP.NET only lives for milliseconds while the
related page is being rendered on the server. If you need an object to live
a long time then you might consider creating a windows service with which
ASP.NET can interact.
Here's more info on windows services:
http://msdn2.microsoft.com/en-us/library/aa983650(VS.71).aspx