Assembly: System (in System.dll)
The signal to raise the Elapsed event is always queued for execution on a ThreadPool thread. This might result in the Elapsed event being raised after the property is set to false. The code example for the Stop method shows one way to work around this race condition.
If the interval is set after the Timer has started, the count is reset. For example, if you set the interval to 5 seconds and then set the property to true, the count starts at the time is set. If you reset the interval to 10 seconds when count is 3 seconds, the Elapsed event is raised for the first time 13 seconds after was set to true.
Some visual designers, such as those in Microsoft Visual Studio, set the property to true when inserting a new Timer.
The following code example sets up an event handler for the Timer.Elapsed event, creates a timer, and uses the event to start the timer. The event handler displays the SignalTime property each time it is raised.
Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012, Windows 7, Windows Vista SP2, Windows Server 2008 (Server Core Role not supported), Windows Server 2008 R2 (Server Core Role supported with SP1 or later; Itanium not supported)