大网数据广告活动
域与目录服务

Dual Interfaces (ADSI)

· 52CE 我爱测

Use COM interfaces to access the properties and methods on any provider ADSI objects.

Use COM interfaces to access the properties and methods on any provider ADSI objects. A read-only property maps to an interface entry of the form get_<PropertyName>. A read/write property maps to two interface entries of the form get_<PropertyName> and put_<PropertyName>.

All methods on a COM interface must:

  • Return an HRESULT value to indicate success or failure. The HRESULT type is discussed in the COM specification.
  • On calls to QueryInterface, return E_NOINTERFACE for unimplemented interfaces.
  • Return E_NOTIMPL for unimplemented methods on interfaces that are otherwise implemented.
  • Return E_ADS_PROPERTY_NOT_SUPPORTED for interface properties that are not supported.

To retain compatibility with Automation controllers, all parameters and return types should be within the subset defined by the Automation VARIANT data type. For more information, see VARIANT and VARIANTARG in the Platform Software Development Kit (SDK).

A provider Active Directory object can expose interfaces that use data types other than those in the VARIANT subset. However, Automation controllers such as Visual Basic are not able to call those interfaces. Most ADSI provider interfaces are derived from IDispatch and can be used as IDispatch interface pointers. However, the IDirectoryObject, IDirectorySearch, and IADsExtension ADSI interfaces are not derived from IDispatch.

Source: Microsoft Learn / Windows Win32 documentation by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / Windows Win32 documentation
适用范围
Windows Win32 API · Source date 05/31/2018
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。