Timer.Enabled Property
Namespace: System.Timers
Assembly: System (in System.dll)
| Exception | Condition |
|---|---|
| ObjectDisposedException | This property cannot be set because the timer has been disposed. |
| ArgumentException | The Interval property was set to a value greater than Int32.MaxValue before the timer was enabled. |
Setting Enabled to true is the same as calling Start, while setting Enabled to false is the same as calling Stop.
.gif?cs-save-lang=1&cs-lang=fsharp "Note") Note |
|---|
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 Enabled property is set to false. The code example for the Stop method shows one way to work around this race condition. |
If Enabled is set to true and AutoReset is set to false, the Timer raises the Elapsed event only once, the first time the interval elapses.
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 Enabled property to true, the count starts at the time Enabled 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 Enabled was set to true.
| Note |
|---|
Some visual designers, such as those in Microsoft Visual Studio, set the Enabled 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 Enabled event to start the timer. The event handler displays the SignalTime property each time it is raised.
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)
The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.
