about System.Threadin g.Timer interval

[violin wang]

hi
When I set up a timer in my program, I used public
Timer(TimerCall back, object, TimeSpan, TimeSpan)
constructor. I want the timer to fire after a mount of
time, so I wrote "new Timer(new TimeCallback
(some_function) , null, timeDiff, new TimeSpan)".When I
ran the program, VS.NET popped a MsgBox that told me the
timer interval must be less than 2^32-2.Actually, the
argument "timeDiff" could be very large(maybe 2 or 3
years).How can I dealing with this problem?

thanks
violin

[Jon Skeet [C# MVP]]

violin wang <an*******@disc ussions.microso ft.com> wrote:

When I set up a timer in my program, I used public
Timer(TimerCall back, object, TimeSpan, TimeSpan)
constructor. I want the timer to fire after a mount of
time, so I wrote "new Timer(new TimeCallback
(some_function) , null, timeDiff, new TimeSpan)".When I
ran the program, VS.NET popped a MsgBox that told me the
timer interval must be less than 2^32-2.Actually, the
argument "timeDiff" could be very large(maybe 2 or 3
years).How can I dealing with this problem?

I'd suggest having a timer which actually fired once a day, only going
for the "accurate" real firing time when it was less than a day away.
That way there'd be less chance of missing the correct time due to
clock changes, time resynchronizati on etc.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Alan Pretre]

"violin wang" <an*******@disc ussions.microso ft.com> wrote in message
news:03******** *************** *****@phx.gbl.. .

When I set up a timer in my program, I used public
Timer(TimerCall back, object, TimeSpan, TimeSpan)
constructor. I want the timer to fire after a mount of
time, so I wrote "new Timer(new TimeCallback
(some_function) , null, timeDiff, new TimeSpan)".When I
ran the program, VS.NET popped a MsgBox that told me the
timer interval must be less than 2^32-2.Actually, the
argument "timeDiff" could be very large(maybe 2 or 3
years).How can I dealing with this problem?

There's a different Timer() constructor that takes 64-bit values. You can
use that instead of TimeSpan.

http://msdn.microsoft.com/library/en...ctortopic2.asp

-- Alan

[Alan Pretre]

"Jon Skeet [C# MVP]" <sk***@pobox.co m> wrote in message
news:MP******** *************** @msnews.microso ft.com...

I'd suggest having a timer which actually fired once a day, only going
for the "accurate" real firing time when it was less than a day away.
That way there'd be less chance of missing the correct time due to
clock changes, time resynchronizati on etc.

It's doubtful the computer will even be up and running that long anyway
without needing to be rebooted... Every Windows Update makes you reboot.

-- Alan

[Jon Skeet [C# MVP]]

Alan Pretre <no@spam> wrote:

"Jon Skeet [C# MVP]" <sk***@pobox.co m> wrote in message
news:MP******** *************** @msnews.microso ft.com...

I'd suggest having a timer which actually fired once a day, only going
for the "accurate" real firing time when it was less than a day away.
That way there'd be less chance of missing the correct time due to
clock changes, time resynchronizati on etc.

It's doubtful the computer will even be up and running that long anyway
without needing to be rebooted... Every Windows Update makes you reboot.

That was my feeling as well, but maybe the OP has some special set of
circumstances :)

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[violin wang]

-----Original Message-----
violin wang <an*******@disc ussions.microso ft.com> wrote:

When I set up a timer in my program, I used public
Timer(TimerCall back, object, TimeSpan, TimeSpan)
constructor. I want the timer to fire after a mount of
time, so I wrote "new Timer(new TimeCallback
(some_function) , null, timeDiff, new TimeSpan)".When I
ran the program, VS.NET popped a MsgBox that told me the timer interval must be less than 2^32-2.Actually, the
argument "timeDiff" could be very large(maybe 2 or 3
years).How can I dealing with this problem?
I'd suggest having a timer which actually fired once a

day, only goingfor the "accurate" real firing time when it was less than a day away.That way there'd be less chance of missing the correct time due toclock changes, time resynchronizati on etc.
Thank you very much.--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too
.