vcruntime140.dll vs msvcr100.dll

[think]

In recent releases I see vcruntime140.dll replaced msvcr100.dll in the package.

What should now be included with the compiled application? None, both or vcruntime140.dll only?

[HotKeyIt]

vcruntime140.dll only!

[robodesign]

Why was this transition made to the new DLL?

I also found that there are versions of these two DLLs that are officially signed. And the ones included in the AHK-H package are not.

Do you compile a specific edition of the DLL?

I noticed no issues if I use the officially signed version of the DLLs.....(tested this only with MSVCR100. DLL, because I've not yet transitioned to the latest AHK-H) ....

Best regards, Marius.

[HotKeyIt]

New dll is because AHK_H is now compiled in VS2017 so others can easily recompile.
The old dll was for VS2010 and taken from SDK, so it was not signed back then.
You can install official runtime without problems.

[robodesign]

Thank you for the reply.

So, I understand the DLL you package now is signed?

[HotKeyIt]

Yes.

[robodesign]

Great to hear, this helps with publishing on windows store where the DLL must be signed....