Win32 C++ 中 COM 的初始化和使用DLL
我正在编写一个 Win32 C++ DLL,它使用 COM 来查询 WMI。如何以编程方式确定 COM 是否已初始化?谢谢。
I am writing a Win32 C++ DLL that uses the COM to query WMI. How can I programmatically determine if COM has already been initialized? Thanks.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(4)
马克·兰塞姆是对的
直接、干净且简单的解决方案是要求调用者初始化 COM。
丑陋的黑客
您可以尝试第一次调用 - 可能是
CoCreateInstance
,如果它返回 CO_E_NOTINITIALIZED,请自行运行CoInitialize
(在这种情况下不要忘记取消初始化)但是< /em>,将 CoInitialize 从 DLL“注入”到调用者线程中仍然存在问题。所以有一个
干净的解决方案
让 DLL 创建一个工作线程(这意味着 DLL 需要 Init 和 Teardown 调用),自己在该线程中进行 CoInitializeEx,并将所有 COM 调用移至该单独的线程。
Mark Ransom is right
the straightforward, clean and simple solution is to require COM initialization by the caller.
Ugly hack
You can try your first call - likely
CoCreateInstance
, and if it returns CO_E_NOTINITIALIZED, runCoInitialize
yourself (and don't forget to uninit in that case)However, it is still problematic to "inject" a CoInitialize into a caller thread from a DLL. So there's a
Clean Solution
Let the DLL create a worker thread (which means the DLL needs Init and Teardown calls), CoInitializeEx in this thread yourself, and move all the COM calls to that separate thread.
最简单的方法就是不要打扰,只需要求任何使用您的 DLL 的人首先初始化 COM。否则,如果他们在您的初始化之后执行初始化,您将面临搞乱自己的初始化的风险。
另一方面,如果您的
CoInitializeEx
标记与应用程序的标记匹配,则应该没问题。来自CoInitializeEx
文档< /a>:The easiest way is not to bother, just make it a requirement of anybody using your DLL that they initialize COM first. Otherwise you run the risk of messing up their own initialization if they perform it after yours.
On the other hand if your flags to
CoInitializeEx
match those of the application, you should be fine. From theCoInitializeEx
documentation:它遵循 @peterchen clean 解决方案,因为我为我想要包装的线程安全 COM 记录器组件编写了它:
It follows @peterchen clean solution as I coded it for a thread-safe COM logger component that I wanted to wrap:
CoInitializeEx\CoUninitialize 只能由线程调用(而不是由 Dll 调用)。
顺便说一句,你不应该在 DllMain 中使用 CoInitializeEx\CoUninitialize !
CoInitializeEx\CoUninitialize should only be called by threads (not by Dll-calls).
BTW ,you should not Use CoInitializeEx\CoUninitialize in DllMain !