This is not a bug, but looks a lot like one. The Microsoft documentation says that the ITaskRegistrationInfo::Date property is set when a task is registered. It appears that this is not the case and that that value, if never set, will always return 'null' which translates in the library to DateTime.MinValue. So, as a work around, in the next release, the Task class exposes a new method, GetLastRegistrationTime(), which will go through all known paths to try and determine when the task was last registered. Given that it may have to comb through the entire event log, this method could take a bunch of time. If task event logging is not enabled for the machine, this method won't give any more information than that which can be retrieved via the Date property.
↧