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

Late Binding Support

· 52CE 我爱测

When late binding support is in place, each function call must go through the ADSI IDispatch interface, before it is rerouted to the appropriate extension.

When late binding support is in place, each function call must go through the ADSI IDispatch interface, before it is rerouted to the appropriate extension.

Consider the following code example.

Set x = GetObject("LDAP://CN=JeffSmith, OU=Sales, 
                   DC=Fabrikam,DC=COM")
x.SetPassword("newPassword")
 
 
x.MyNewMethod( "\\srv\public")
x.MyProperty = "Hello World"
 
x.OtherMethod()
x.OtherProperty = 4362
 
Debug.Print x.LastName

There are no explicit calls to the QueryInterface method to get to the extensions. The extensions must reroute their IDispatch calls to the ADSI IDispatch interface. ADSI makes the decision and resolves any conflicts that occur, then it re-routes back to the appropriate extension using an interface called IADsExtension. Therefore, any extension that supports late binding must implement IADsExtension.

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)

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

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