In Microsoft System Center Configuration Manager 2007, when you write unmanaged applications, you might have to include one or more of the following libraries, which are included with the Configuration Manager SDK. Use COM Interop to access COM objects from .NET Framework applications.
| Library | Description |
|---|---|
|
SMSRsGen.dll |
Contains the Discovery Data Record functions. This DLL must exist in the directory from where you start your application. |
|
SMSRsGenCtl.dll |
Contains a class wrapper for the Discovery Data Record Functions. Visual Basic and scripting programmers use this control to create discovery data records. For more information, see Discovery Server COM Automation Classes. |
|
ISMIFCOM.dll |
Contains a class wrapper for the install status MIF functions. Visual Basic and scripting programmers use this ActiveX control to create a status MIF file. Visual Basic users must select the ISMIFCOM 1.0 Type Library project reference. Scripting users create this object by using "ISMIFCOM.InstallStatusMIF". |
|
Tsmediaapi.dll |
Contains task sequence media functions. For more information, see Operating System Deployment Media Management. |
|
Mpapi.msi |
Contains management point interface libraries. For more information, see Configuration Manager Management Point Interface. |
You might have to include one or more of the following header files, which are included with the Configuration Manager SDK.
| Header file | Description |
|---|---|
|
Ssperrcode.h |
Contains the error codes and macros that are used to evaluate an error condition that is returned from the SMS Provider. |
|
Smscstat.h |
Contains header information for creating status messages. For more information, see About Using SMSCSTAT.DLL to Create Status Messages. |
See Also
Send comments about this topic to Microsoft.