Creating an IIS ADSI Extension Method to Support Late Binding
There are two levels of Automation that your extension can support: early and late binding. Adding support for late binding tools, such as VBScript, JScript?, and so on, requires more work than adding an early binding extension. You must add support for the IADsExtension interface and delegate IDispatch in the same way that IUnknown is delegated for early binding. At the time of this writing, the Active Template Library (ATL) didn't provide support for delegating internal IDispatch activity, so you will probably need to provide this functionality.
Note
If you are creating a new extension you will need to review Creating an Extension Method to Support Early Binding. This may not be necessary if you need only to add late binding support to an existing extension.
If your extension supports late binding, it can be accessed by using late binding Automation clients, such as Windows Script Host, Active Server Pages, and VBScript, as well as by early binding tools, such as Visual Basic? and Visual C++?.
The following is an example of late binding code for accessing your extension:
Set MyObj = GetObject("IIS://LM/W3SVC")
Debug.Print MyObj.LastBackup
MyObj.Backup
This section includes the following topics: