Question

我正在参加一个过程:COMCTL32.DL两次装载,一次装上5.82.7601.17514版本,一次装上6.10.7601.17514版本。遗产版本由一些遗留下来的DLL组成,该方案与新的DLLL联系,而另一个版本则由新的DLL组成。

If I use GetModuleHandle (L"COMCTL32.DLL") I have no control over the DLL which gets resolved.

When I call GetProcAddress to reach, for instance, TaskDialogIndirect, I get a null pointer back, which is certainly because I got back the handle of the legacy DLL.

因此,有某种手段去读到TaskDialogIndirect的地址。这两辆DLLL车都装载。

If not, can I somehow make sure that the process loads the 6.10 version and not the 5.82, in the hope that our legacy DLL will work fine with the newer version of COMCTL32?

Answer 1

I guess you are having to use GetProcAddress() rather than implicit linking because you want your app to run on XP where task dialog is not available.

I can see three options for you:

Use implicit linking, but use delay loading as supported by the MS tool chain. I m not 100% certain that will give you the correct comctl32 but it s worth a try.
Use the activation context API to make sure that the comctl32 v6 manifest is in play when you call LoadLibrary(). Call LoadLibrary() rather than GetModuleHandle() to make sure that you get the manifest magic.
Enumerate all the modules in the process and select the correct version of comctl32. There is a comprehensive example of how to do this on MSDN.

生态环境办法是最清洁的解决办法,但环境分析模型可以渗透进来。我个人利用了这一系统,确保了一家Excel COM公司与Cectl32 v6的链接。

模块列举办法迅速实施,有些过于仓促,但效果良好。

友情链接