[Bug 35252] Multiple applications need ITaskScheduler::Enum implementation (lsTasks, Toad for MySQL Freeware 7.2)

https://bugs.winehq.org/show_bug.cgi?id=35252

--- Comment #5 from Dmitry Timoshkov  ---
(In reply to Nikolay Sivov from comment #4)
> Either way works for me. Now it made me think if mstask should forward to
> newer interfaces from taskschd. If they are different APIs that work on same
> data we should consider using taskschd as it got more implemented features.

Yes, mstask should be implemented using taskschd, one of the most notable
reasons is that they are using the same task database. v1 to v2+ API mapping
is reasonably simple. Probably v1 task enumeration needs some filtering to
avoid listing v2+ tasks, but that's also pretty obvious and easy to do.