Many bug fixes, better localization support (adding Chinese), and Task Scheduler 1.0 support for XML since the 1.7.1 release. See Source Code
for full details of changes. Also, all assemblies are now strongly named.Download Descriptions
Potentially Breaking ChangesThere is a remote chance that some of the changes in this release may break your code. Please check if you have code that:
- TaskScheduler.zip - Includes the base library (Microsoft.Win32.TaskScheduler.dll) with no UI code. Works with .NET 2.0 and higher. Add this assembly as a reference to interact with Task Scheduler on all systems with IE4 and later. This package is also available via NuGet with package name TaskScheduler.
- TaskSchedulerEditor.zip - Includes the UI library (Microsoft.Win32.TaskSchedulerEditor.dll) with all supporting assemblies. Works with .NET 3.5 and higher. Add this assembly as a reference along with Microsoft.Win32.TaskScheduler.dll to get editor controls and dialogs that allow for viewing and editing tasks, triggers, actions, lists, etc. This package is also available via NuGet with package name TaskSchedulerEditor.
- TaskSchedulerHelp.zip - Includes the Microsoft Help (VS2010) compatible help files for both the base and editor libraries. Extract all files and then run Install_TaskScheduler.bat to integrate the help.
- Makes specific assumptions about the underlying Kind (Utc, Local) of DateTime values for Trigger.StartBoundary and Trigger.EndBoundary.
- Provides username, domain and password for connecting to remote servers. You must have all three as non-null, valid strings or all null.
- V1 only: Assumes Task.State property does not provide the dynamic state of the task
- V1 only: Assumes Task.Enabled property does not take effect until re-registering the task.
- (1.8.2) Task.NextRunTime. For Task Scheduler 2.0, the return value was Dec 30, 1899 if there were no future run times. For 1.0, that value would have been DateTime.MinValue. Now all versions will return DateTime.MinValue if there are no future run times. While this is different from the native 2.0 library, it was deemed more appropriate to have consistency between the two libraries and with other .NET libraries.
- (1.8.3) A number of the properties and methods related to reading and writing Xml that once threw NotV1SupportedException will now process the Xml.