What is the different between 'IsEnabled' and 'Start/Stop' of DispatcherTimer?

Considering that Start/Stop toggles the IsEnabled property, your assumption is close.

Start/Stop differs as the Interval is reset, where as just toggling the IsEnabled will not reset the Interval.

From MSDN:

Setting IsEnabled to false when the timer is started stops the timer.

Setting IsEnabled to true when the timer is stopped starts the timer.

Start sets IsEnabled to true.

Start resets the timer Interval.

EDIT:What I mean by the interval being reset is not the Interval property itself, but the background interval that determines how long until the next tick event is fired.

Eg. If you have an interval of 1000ms and you stop/disable it if with 250ms to run (it's run for 750ms), this is the result depending on how you start it again.

• If you start it with Start(), then the passed interval will be reset back to 0 and it will be 1000ms before the Tick event is raised.
• If you re-enable it with IsEnabled = true then it will continue from it's current location and the Tick event will be raised in 250ms.

I hope this clarifies it for you.

Implementation of DispatcherTimer.IsEnabled

    public bool IsEnabled    {       get       {           return _isEnabled;       }       set       {           lock (_instanceLock)           {               if (!value && _isEnabled)               {                   Stop();               }               else               {                   if (!value || _isEnabled)                       return;                   Start();               }           }       }    }