Life Scope

[Chan]

In MS' TimeTracker sample app, a middle-tier component BLL has a class
named TimeEntry. It's used in TimeEntry.aspx to remember a certain
state of an entry.
I'm wondering

1> what's the life scope of TimeEntry, and when it will be scraped?

2> how do we tell the GC not to touch it?

 

[Alvin Bruney [MVP]]

Your post went unanswered. Have you resolved this issue?

 

[Chan]

No, not yet.

There is no Session_End to handle it.

Any input?

Thanks!

 

[Alvin Bruney [MVP]]

I'd be willing to help you if you could just repost the original question.

 

[Chan]

Alvin,

Here is my original post >>>>>>>>>>>>>>>>>

In MS' TimeTracker sample app, a middle-tier component BLL has a class
named TimeEntry. It's used in TimeEntry.aspx to remember a certain
state of an entry.
I'm wondering

1> what's the life scope of TimeEntry, and when it will be scraped?

2> how do we tell the GC not to touch it?

<<<<<<<<<<<<<<<<<<<<<<

Thank you for your help!

 

[Alvin Bruney [MVP]]

timetracker.aspx is built into a dll upon an initial request for that page.
Once the page is served, it is cached for further use. If there is a period
of inactivity, the cache is cleared and the reference to the dll is removed
from scope.

To prevent the GC from collecting, simply maintain a reference to the
assembly. Be careful though because it won't be collected unless the
reference goes away leading to a potential memory leak.