Hi Darko ,
As for this post, I've seen one of your former thread regarding on the same
question. Some community members and I have posted our replies there. Have
you had a chance to have a look there? Anyway, I've pasted my reply in the
following, please let me know if you have any new ideas on this:
=====================================
Hi Darko,
I think Gabriel's suggestion on using a Timer is good. Also, the article
Gabriel provided seems discussing on desktop application scenario, as for
asp.net web application, that's a bit different from desktop application
when using Timer object. ASP.NET application is request/response based
which dosn't as persistent connection between client and server. So after a
certain page's execution lifecycle (render response to client), the page
object at serverside will be disposed. So if we will use Timer at
serverside, don't create it as local variable in page
class (as member or local variable in function). We can use the following
means to hold the reference to the Timer:
1. Use a certain class's static member which will be global to all the
classes in your application( if not using webfarm ).
2. Use the asp.net's Application Cache or ApplicationState to store the
reference of the Timer you created
In addition to using Timer, we can also create a background thread in
asp.net which constantly check some schedule tasks. The thread's reference
can also be held through the means I mentioned above.
If there are anything unclear, please feel free to post here. Hope helps.
=====================================
Thanks,
Steven Cheng
Microsoft Online Support
Get Secure!
www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
