Programming Considerations
Collapse the table of content
Expand the table of content

Programming Considerations

When developing applications that use the Task Scheduler 1.0, keep the following programming issues in mind.

  • Your application must ensure the Task Scheduler service is running before attempting to make any calls using the Task Scheduler API.
  • When retrieving strings, make sure that you call CoTaskMemFree to release each string after it is no longer needed. When retrieving arrays of strings, make sure you first release each string in the array and then release the array itself.
  • When creating or modifying a work item, including triggers associated with a work item, make sure you call IPersistFile::Save to save the work item to disk.
  • After using any of the interfaces that are provided by the Task Scheduler API, make sure you call IUnknown::Release to release the interface. IUnknown is supported by each Task Scheduler object.

The Using section of the Task Scheduler documentation provides numerous examples that follow these guidelines. The table below provides jumps to some of these examples.

For an example ofSee
Releasing strings Retrieving Work Item Property Examples
Saving work items to disk Setting Work Item Property Examples
Releasing interfaces Creating a Task Using NewWorkItem Example

 

 

 

Community Additions

ADD
Show:
© 2016 Microsoft