The IMofCompiler interface is implemented by mofd.dll. It provides a COM interface which is used by the MOF Compiler and any other applications which need to compile MOF files. Objects can be obtained using the CLSID_MofCompiler CLSID.

The IMofCompiler::QueryInterface method determines if the object supports a particular COM interface. If it does, the system increases the object's reference count, and the application can use that interface immediately.

[in] REFIID riid,

[out] LPVOID *ppv

Address of a pointer that will be filled with the interface pointer if the query succeeds.

Returns standard COM error codes for QueryInterface. It returns WBEM_S_NO_ERROR if the call succeeds. If the call fails because the requested interface was not supported, the method returns E_NOINTERFACE.

When the application no longer needs the interface retrieved by a call to this method, it must call the Release method for that interface to free it. The QueryInterface method allows the extension of objects without interfering with each object's existing or future functionality.

This method is part of the IUnknown interface inherited by the object. For more information about this method, see the COM documentation in the Microsoft Platform SDK.

The IMofCompiler::AddRef method increases the object's reference count by 1.

None.

Returns the new reference count.

This method is part of the IUnknown interface inherited by the object. For a complete discussion of IUnknown methods, see IUnknown Programming Basics.

For more information about this method, see the COM documentation in the Microsoft Platform SDK.

The IMofCompiler::Release method decreases the object's reference count by 1.

None.

Returns the new reference count.

This method is part of the IUnknown interface inherited by the object. For more information about this method, see the COM documentation in the Microsoft Platform SDK.

This method compiles a MOF file (including binary MOFs) and stores the information into WINMGMT.

);

Name of the file to be compiled.

Path to the default namespace where any classes or instance are to be written. A namespace on remote machine can be specified. Ex; "\\computer\root". This value may be overriden by pragmas and should not be used if auto recovery is desired. If NULL, then the ROOT\DEFAULT namespace on the local machine is the default.

Used to specify credentials for compiling on remote machines. If NULL, then the user context is whatever the calling process is using. This is always ignored when connecting to the local machine. See the remarks.

Used to specify credentials for compiling on remote machines. If NULL, then the Authority context is whatever the calling process is using. This is always ignored when connecting to the local machine. See the remarks.

Used to specify credentials for compiling on remote machine. If NULL, the password of the current context is used. This is always ignored when connecting to the local machine.

lOptionFlags

One or more of the following flags may be combined:

WBEM_FLAG_CHECK_ONLY – Performs a syntax check only

WBEM_FLAG_AUTORECOVER – If successful, add the name of the file to the list of files to that are to be compiled during data base autorecovery. Note that this cannot be combined with either the namespace, class or instance flags.

WBEM_FLAG_CONSOLE_PRINT – If set, various useful messages are output to the console.

WBEM_FLAG_DONT_ADD_TO_LIST – If set, the file will not be added to the list of files to be compiled during auto recovery. This is not compatible with WBEM_FLAG_AUTORECOVER.

Flags controlling the creation of classes. May be 0 or a combination of:

WBEM_FLAG_UPDATE_ONLY – Class creation is not allowed. May be combined with either WBEM_FLAG_UPDATE_SAFE_MODE or WBEM_FLAG_UPDATE_FORCE_MODE.

WBEM_FLAG_CREATE_ONLY – Only class creation is allowed. May not be combined with the other flags.

WBEM_FLAG_UPDATE_SAFE_MODE – Update unless conflicts exist. May be combined with WBEM_FLAG_UPDATE_ONLY.

WBEM_FLAG_UPDATE_FORCE_MODE – Update and resolve conflicts where possible. May be combined with lInstanceFlags.

Flags controlling the creation of instances. May be either 0 or one of the following:

WBEM_FLAG_UPDATE_ONLY – Allow only updates.

WBEM_FLAG_CREATE_ONLY – Allow only new instances.

If not NULL, then this is filled in with error information should an error occur. Note that the ObjectNum, FirstLine, and LastLine only contain values for errors that relate to a particular class of instance in the file.

struct

{

long lPhaseError; // 0 = no error, 1 = argument error, 2 = parsing, 3 error occurred while storing the data

HRESULT hRes; // Actual error code

long ObjectNum; // object which is at fault

long FirstLine; // first line number of the object

long LastLine; // last line number of the object

DWORD dwOutFlags; // reserved

} WBEM_COMPILE_STATUS_INFO; 

WBEM_S_NO_ERROR. Success.

WBEM_S_FALSE. Failure.

The User argument may be of the form "domain\user". If that is the case, then the authority field must be NULL.

This method compiles a buffer containing binary MOF data. Binary MOFs contain parsed data and only needs to be stored in the database.

);

Size of the data pointed to by the pBuffer argument.

A pointer to the binary MOF data.

ServerAndNamespace,

Ignored since the binary MOF contains the information already. Should be NULL.

Used to specify credentials for compiling on remote machines. If NULL, then the user context is whatever the current process is using. This is always ignored when connecting to the local machine. See the remarks.

Used to specify credentials for compiling on remote machines. If NULL, then the Authority context is whatever the current process is using. This is always ignored when connecting to the local machine. See the remarks.

Used to specify credentials for compiling on remote machine. If NULL, the password of the current context is used. This is always ignored when connecting to the local machine.

lOptionFlags

One or more of the following flags may be combined:

WBEM_FLAG_CHECK_ONLY – Performs a syntax check only

WBEM_FLAG_AUTORECOVER – If successful, add the name of the file to the list of files to are to be compiled during data base autorecover. Note that this cannot be combined with either the namespace, class or instance flags.

WBEM_FLAG_CONSOLE_PRINT – If set, various useful messages are output to the console.

WBEM_FLAG_DONT_ADD_TO_LIST – If set, the file will not be added to the list of files to be compiled during auto recovery. This is not compatible with WBEM_FLAG_AUTORECOVER.

Ignored since the binary MOF contains the information already. Should be 0.

lInstanceFlags

Ignored since the binary MOF contains the information already. Should be 0.

If not NULL, then this is filled in with error information should an error occur. Note that the ObjectNum, FirstLine, and LastLine only contain values for errors that relate to a particular class of instance in the file.

struct

{

long lPhaseError; // 0 = no error, 1 = argument error, 2 = parsing, 3 error occurred while storing the data

HRESULT hRes; // Actual error code

long ObjectNum; // object which is at fault

long FirstLine; // first line number of the object

long LastLine; // last line number of the object

DWORD dwOutFlags; // reserved

} WBEM_COMPILE_STATUS_INFO; 

WBEM_S_NO_ERROR. Success.

WBEM_S_FALSE. Failure.

The User argument may be of the form "domain\user". If that is the case, then the authority field must be NULL. Binary MOF data can be generated by CreateBMOF function. That function, stores the binary MOF data into a file, which may be read before calling this functions.

This creates a binary MOF file. This is done, by parsing a regular MOF file, and storing a binary representation of the classes and instances into a special file format. Typically, this data blob is stored as a resource in an executable file. That resource can latter be extracted for a call to CompileBuffer.

);

Name of the text file, which is to be parsed.

Name of the file where the resulting binary MOF data is to be stored.

Path of the default namespace where any classes or instance are to be written. This can be used to specify a namespace on a remote machine. Ex; "\\computer\root". This value may be over riden by pragmas and should not be use if auto recovery is desired. If NULL, then the ROOT\DEFAULT namespace on the local machine is the default.

lOptionFlags

One or more of the following flags may be combined;

WBEM_FLAG_CHECK_ONLY – Performs a syntax check only

WBEM_FLAG_CONSOLE_PRINT – If set, various useful messages are output to the console.

WBEM_FLAG_WMI_CHECK – If set, additional checks are done on the resulting binary MOF file using the WMIMOFCHK program which is part of the WMI SDK.

Flags controlling the creation of classes. May be 0 or a combination of:

WBEM_FLAG_UPDATE_ONLY – Class creation is not allowed. May be combined with either WBEM_FLAG_UPDATE_SAFE_MODE or WBEM_FLAG_UPDATE_FORCE_MODE.

WBEM_FLAG_CREATE_ONLY – Only class creation is allowed. May not be combined with the other flags.

WBEM_FLAG_UPDATE_SAFE_MODE – Update unless conflicts exist. May be combined with WBEM_FLAG_UPDATE_ONLY.

WBEM_FLAG_UPDATE_FORCE_MODE – Update and resolve conflicts where possible. May be combined with lInstanceFlags

lInstanceFlags

Flags controlling the creation of instances. May be either 0 or one of the following:

WBEM_FLAG_UPDATE_ONLY – Allow only updates.

WBEM_FLAG_CREATE_ONLY – Allow only new instances.

If not NULL, then this is filled in with error information should an error occur. Note that the ObjectNum, FirstLine, and LastLine only contain values for errors that relate to a particular class of instance in the file.

struct

{

long lPhaseError; // 0 = no error, 1 = argument error, 2 = parsing, 3 error occurred while store the data

HRESULT hRes; // Actual error code

long ObjectNum; // object which is at fault

long FirstLine; // first line number of the object

long LastLine; // last line number of the object

DWORD dwOutFlags; // reserved

} WBEM_COMPILE_STATUS_INFO; 

WBEM_S_NO_ERROR. Success.

WBEM_S_FALSE. Failure.