将COM事件暴露给VBScript(ATL) [英] Exposing COM events to VBScript (ATL)

查看:203
本文介绍了将COM事件暴露给VBScript(ATL)的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已经使用ATL简单对象向导在C ++中使用ATL构建了一个COM服务器DLL。我按照Microsoft的 ATLDLLCOMServer 示例。一切都很好,除了一件事:我没有收到COM事件在VBScript 。我收到的事件在C#。我有一个事件工作在VBScript在早期的基于MFC的实现作为ActiveX控件。



我的控制定义如下:

 类ATL_NO_VTABLE CSetACLCOMServer:
公共CComObjectRootEx< CComSingleThreadModel>中
公共CComCoClass< CSetACLCOMServer,&安培; CLSID_SetACLCOMServer>中
公共IConnectionPointContainerImpl< CSetACLCOMServer> ,
公共CProxy_ISetACLCOMServerEvents< CSetACLCOMServer>中
公众的IDispatchImpl< ISetACLCOMServer,&安培; IID_ISetACLCOMServer,&安培; LIBID_SetACLCOMLibrary,/ * wMajor = * / 1 / * wMinor = * / 0>中
公IProvideClassInfo2Impl<& CLSID_SetACLCOMServer,& DIID__ISetACLCOMServerEvents,& LIBID_SetACLCOMLibrary> / *为必填在VBS * /
{
公众活动的支持:

BEGIN_COM_MAP(CSetACLCOMServer)
COM_INTERFACE_ENTRY(ISetACLCOMServer)
COM_INTERFACE_ENTRY(IDispatch接口)
COM_INTERFACE_ENTRY(的IConnectionPointContainer)
COM_INTERFACE_ENTRY(IProvideClassInfo)
COM_INTERFACE_ENTRY(IProvideClassInfo2)
END_COM_MAP()

BEGIN_CONNECTION_POINT_MAP(CSetACLCOMServer)
CONNECTION_POINT_ENTRY(__ uuidof( _ISetACLCOMServerEvents))
END_CONNECTION_POINT_MAP()

[...]

在VBScript中我使用COM对象像这样:

  set objSetACL = WScript.CreateObject(SetACL.SetACL SetACL_)

'从SetACL COM服务器捕获并打印作为事件传递(触发)的消息。
'此函数的名称后缀(MessageEvent)必须与SetACL定义的事件名称
'相同。
'前缀(SetACL_)可以在调用WScript.CreateObject时自由设置
sub SetACL_MessageEvent(Message)
WScript.Echo消息
end sub

IDL的相关部分如下:

  [
object,
uuid(E1B57CA5-FD7F-4304-BC0A-8BEBDE231D53),
dual,
不可扩展,
pointer_default ),
helpstring(SetACL COM Interface)
]
interface ISetACLCOMServer:IDispatch
{
}

[
uuid(00D4DCD3-02B9-4A71-AB61-2283504620C8),
版本(1.0),
helpstring(SetACL类型库)
]
library SetACLCOMLibrary
{
importlib(stdole2.tlb);

[
UUID(35F76182-7F52-4D6A-BD6E-1317345F98FB),
helpstring(SETACL事件接口)
]
调度接口_ISetACLCOMServerEvents
{
属性:
方法:
[ID(1),helpstring(接收,将出现在命令行版本在屏幕上线的消息)]
void MessageEvent([in] BSTR message);
};

[
uuid(13379563-8F21-4579-8AC7-CBCD488735DB),
helpstring(SetACL COM Server),
]
coclass SetACLCOMServer
{
[默认] interface ISetACLCOMServer;
[default,source] dispinterface _ISetACLCOMServerEvents;
};
};

问题:SetACL_MessageEvent从未被调用。



我尝试了:





更新1: b

我现在知道它在哪里失败,但不是为什么:在_ISetACLCOMServerEvents_CP.h中的fire事件方法中,对Invoke的调用失败,并显示E_UNEXPECTED。这是行:

  hr = pConnection-> Invoke(1,IID_NULL,LOCALE_USER_DEFAULT,DISPATCH_METHOD,& params,NULL ,NULL,NULL); 

解决方案:



问题是我所谓的事件从COM对象的后台线程发射功能,从错误的公寓等字样。


解决方案

IProvideClassInfo2 的实现应该是足够的(虽然我的印象是它应该工作,即使没有它)。我从模板创建了一个简约的ATL项目作为样本。这是ATL DLL + COM类+方法和事件+ IProvideClassInfo2



源代码[ SVN 浏览器支持] + Win32 Binary



测试 .vbs

 函数Test_Event(Text)
WScript.EchoEvent:+ Text


Dim Test
Set Test = WScript.CreateObject(AlaxInfo.VbsEvents.Foo,Test_)
Test.Method(Event Fun)

方法本身是:

 code> // IFoo 
STDMETHOD(方法)(BSTR sText)throw()
{
ATLTRACE(atlTraceCOM,4,_T(sText \%s\ \\\
),CString(sText));
ATLVERIFY(SUCCEEDED(Fire_Event(sText))));
return S_OK;
}

执行此操作后,输出为:



>



我认为如果你从后台线程中触发你的示例项目中的事件,你可能会遇到问题。您还可以使用调试器来调试您的项目,并检查 Fire _ 调用中是否有任何错误。


I have built a COM server DLL in C++ with ATL by using the "ATL simple object" wizard. I followed Microsoft's ATLDLLCOMServer example. Everything works well except for one thing: I do not receive COM events in VBScript. I do receive the events in C#. I had events working in VBScript in an earlier MFC-based implementation as ActiveX control.

My control is defined like this:

class ATL_NO_VTABLE CSetACLCOMServer :
    public CComObjectRootEx<CComSingleThreadModel>,
    public CComCoClass<CSetACLCOMServer, &CLSID_SetACLCOMServer>,
    public IConnectionPointContainerImpl<CSetACLCOMServer>,
    public CProxy_ISetACLCOMServerEvents<CSetACLCOMServer>,
    public IDispatchImpl<ISetACLCOMServer, &IID_ISetACLCOMServer, &LIBID_SetACLCOMLibrary, /*wMajor =*/ 1, /*wMinor =*/ 0>,
    public IProvideClassInfo2Impl<&CLSID_SetACLCOMServer, &DIID__ISetACLCOMServerEvents, &LIBID_SetACLCOMLibrary>   /* Required for event support in VBS */
{
public:

BEGIN_COM_MAP(CSetACLCOMServer)
    COM_INTERFACE_ENTRY(ISetACLCOMServer)
    COM_INTERFACE_ENTRY(IDispatch)
    COM_INTERFACE_ENTRY(IConnectionPointContainer)
   COM_INTERFACE_ENTRY(IProvideClassInfo)
   COM_INTERFACE_ENTRY(IProvideClassInfo2)
END_COM_MAP()

BEGIN_CONNECTION_POINT_MAP(CSetACLCOMServer)
    CONNECTION_POINT_ENTRY(__uuidof(_ISetACLCOMServerEvents))
END_CONNECTION_POINT_MAP()

[...]

In VBScript I use the COM object like this:

set objSetACL = WScript.CreateObject("SetACL.SetACL", "SetACL_")

' Catch and print messages from the SetACL COM server which are passed (fired) as events.
' The name postfix of this function (MessageEvent) must be identical to the event name 
' as defined by SetACL.
' The prefix (SetACL_) can be set freely in the call to WScript.CreateObject
sub SetACL_MessageEvent (Message)
    WScript.Echo Message
end sub

The relevant parts of the IDL look like this:

[
    object,
    uuid(E1B57CA5-FD7F-4304-BC0A-8BEBDE231D53),
    dual,
    nonextensible,
    pointer_default(unique),
   helpstring("SetACL COM Interface")
]
interface ISetACLCOMServer : IDispatch
{
};

[
    uuid(00D4DCD3-02B9-4A71-AB61-2283504620C8),
    version(1.0),
   helpstring ("SetACL Type Library")
]
library SetACLCOMLibrary
{
    importlib("stdole2.tlb");

   [
        uuid(35F76182-7F52-4D6A-BD6E-1317345F98FB),
      helpstring ("SetACL Event Interface")
    ]
    dispinterface _ISetACLCOMServerEvents
    {
        properties:
        methods:
         [id(1), helpstring("Receives string messages that would appear on the screen in the command line version")]
         void MessageEvent([in] BSTR message);
   };

   [
        uuid(13379563-8F21-4579-8AC7-CBCD488735DB),
      helpstring ("SetACL COM Server"),
    ]
    coclass SetACLCOMServer
    {
        [default] interface ISetACLCOMServer;
        [default, source] dispinterface _ISetACLCOMServerEvents;
    };
};

The problem: SetACL_MessageEvent never gets called.

What I have tried:

  • After reading this KB article I added the implementation of IProvideClassInfo2, but that did not help.
  • This FAQ mentions that outgoing interface should not defined as a dual interfaces. I removed the "dual" from my interface definition, but that did not help.
  • I found this SO question that seems to describe a similar problem. An answer was never given, only a workaround.

UPDATE 1:

I know now where it is failing, but not why: in the fire event method in _ISetACLCOMServerEvents_CP.h the call to Invoke fails with E_UNEXPECTED. This is the line:

hr = pConnection->Invoke(1, IID_NULL, LOCALE_USER_DEFAULT, DISPATCH_METHOD, &params, NULL, NULL, NULL);

Solution:

The problem was that I called the event firing function from a background thread in the COM object, in other words from the wrong apartment.

解决方案

Implementation of IProvideClassInfo2 should be sufficient (though I was under impression that it should work even without it). I created a minimalistic ATL project from template as a sample. This is ATL DLL + COM Class + a method and an event + IProvideClassInfo2:

Source code [SVN, Browser Friendly] + Win32 Binary.

Test .vbs is the following:

Function Test_Event(Text)
  WScript.Echo "Event: " + Text
End Function

Dim Test
Set Test = WScript.CreateObject("AlaxInfo.VbsEvents.Foo", "Test_")
Test.Method("Event Fun")

And the method itself is:

// IFoo
    STDMETHOD(Method)(BSTR sText) throw()
    {
        ATLTRACE(atlTraceCOM, 4, _T("sText \"%s\"\n"), CString(sText));
        ATLVERIFY(SUCCEEDED(Fire_Event(sText)));
        return S_OK;
    }

And having executed this, the output is:

I thought you might be having issues with events in your sample project if you are firing them from a background thread. You can also step your project with debugger and check if you have any errors in the Fire_ call.

这篇关于将COM事件暴露给VBScript(ATL)的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆