[[This API may be altered or unavailable in subsequent versions of the operating system or product. Please use the Task Scheduler 2.0 Interfaces instead.] ]
The NewWorkItem method creates a new work item, allocating space for the work item and retrieving its address.
HRESULT NewWorkItem( LPCWSTR pwszTaskName, REFCLSID rclsid, REFIID riid, IUnknown **ppUnk );
A null-terminated string that specifies the name of the new work item. This name must conform to Windows NT file-naming conventions, but cannot include backslashes because nesting within the task folder object is not allowed.
The class identifier of the work item to be created. The only class supported at this time, the task class, has the identifier CLSID_Ctask.
The reference identifier of the interface being requested. The only interface supported at this time, ITask, has the identifier IID_ITask.
A pointer to an interface pointer that receives the requested interface. See Remarks for information on saving the work item to disk.
The NewWorkItem method returns one of the following values.
||The operation was successful.|
||A work item with the specified name already exists. The actual return value is HRESULT_FROM_WIN32 (ERROR_FILE_EXISTS).|
||One or more of the arguments is not valid.|
||Not enough memory is available to complete the operation.|
||The caller does not have permission to perform the operation. For more information, see Scheduled Work Items.|
This method handles memory allocation automatically when creating the new work item.
Task scheduler provides two methods for adding work items: NewWorkItem and AddWorkItem. Of these methods, each has its specific advantage. AddWorkItem prevents naming collisions, but also requires two disk write operations per call. One write operation is performed when the call to AddWorkItem creates an empty work item object on the disk, followed by another write operation when IPersistFile::Save is called.
You can create a task by calling AddWorkItem or NewWorkItem. When use AddWorkItem, it is your responsibility to create an instance of the Task object (which supports the ITask interface) and then add the task with the name you supply.
NewWorkItem does not prevent naming collisions, but requires only one disk write operation when IPersistFile::Save is called. Although NewWorkItem is more efficient with respect to disk write operations, the application runs the risk of having another application create a work item with the same name before the call to IPersistFile::Save is made.
|For a complete example of||See|
|Creating a new task||Creating a Task Using NewWorkItem Example|
|Minimum supported client||Windows 2000 Professional [desktop apps only]|
|Minimum supported server||Windows 2000 Server [desktop apps only]|
|Redistributable||Internet Explorer 4.0 or later on Windows NT 4.0 and Windows 95|