Tym,
No using one of the 3 Timer objects in .NET would be the "best solution in
program"!
There are three distinct timer objects in .NET:
- System.Windows.Forms.Timer
- System.Threading.Timer
- System.Timers.Timer
There is also a Timer function in VB.NET, however it does not really allow
you to schedule an event to occur at a specific time.
Of course using one of the above Timer objects requires that your program
actually be running at the specified time. If the event has to occur I would
probably use Threading.Timer or Timers.Timer in a Windows Service, as the
service will always run, even without anyone logged in, Of course the
machine needs to be physically turned on!
The following article in MSDN Magazine explains the difference between the
three timer objects in .NET & when to use each.
http://msdn.microsoft.com/msdnmag/is...T/default.aspx
The above article also discusses if & how each timer interacts with
threading.
Hope this helps
Jay
"Tym" <no*****@ictis.net> wrote in message
news:gu********************************@4ax.com...
On Tue, 19 Oct 2004 13:14:22 -0500, "CJ Taylor" <[cege] at [tavayn]
dit commmmm> wrote:
Wow...
That will eat up 50% CPU the entire time... [as per framework limitations]
I know - but it's about the best solution "in program" without
resorting to the external scheduler...