IPipeline::SetLogFile
.gif "Ee799619.c++_off(en-US,CS.10).gif")
.gif "Ee799619.vb_on(en-US,CS.10).gif")
Use this method to identify the file in which to log the operations of the pipeline component.
.gif "Ee799619.note(en-US,CS.10).gif")
Note
- This method is for use by developers who want to analyze pipeline configuration file information. Logging should never be used in a production environment: it degrades performance and may compromise the security of credit card numbers in non-set transactions.
Definition
HRESULT IPipeline::SetLogFile(BSTRpszFileName);
Parameters
pszFileName
[in] A BSTR containing the name of the file in which to log events.
Return Values
This method returns an HRESULT indicating whether or not it completed successfully. See the Error Values section for more details.
Error Values
This method returns S_OK (0x00000000) to indicate success and standard COM HRESULT error values to indicate failure. For more information about standard COM errors, see Standard COM Errors. Additional information may be available using the global Err object, which can be accessed using the API function GetErrorInfo. In particular, the GetDescription method of the IErrorInfo interface may return a text description of the error.
Remarks
When logging is set, the pipeline logs the pipeline components that are called and the error values each component returns. The pipeline also logs all Dictionary and SimpleList object read and write operations.
Calling the method with an empty string turns off logging.
The SetLogFile method should be called immediately before executing a pipeline. The SetLogFile method is exposed on the OrderGroup object as the LogFile property and should be set before calling the RunPipe method.
For more information about memory ownership issues related to COM property and method parameters, see Managing COM Parameter Memory.