MSVCP120.dll MSVCR120.dll are missing

Feb 1, 2015 at 3:09 AM
Edited Feb 1, 2015 at 3:21 AM
Hi Jame

It seems that the native dlls are compiled with different version of visual studios.

Check them in the Dependency Walker tool, many of them depends on MSVCP120.dll MSVCR120.dll.

It is better to statically-link C/CPP runtime for all native dlls.

But for for CPP /CLI dlls, if I remember correctly, static link is unavailable. then they must be distributed together, otherwise C/CPP runtime libraries has to be installed first on server.
Coordinator
Feb 1, 2015 at 4:06 AM
I use VS 2013 for everything, and C++/CLI will never be supported, as it is not supported by mono.
Coordinator
Feb 1, 2015 at 4:08 AM
You shouldn't need to install anything else. I already included the required DLLs.
Feb 1, 2015 at 5:36 AM
Edited Feb 2, 2015 at 2:52 AM
Hi James

I downloaded the latest distribution from here

icui18n.dll icuuc.dll, V8_Net_Proxy_x64.dll, v8-x64.dll depend on MSVCP120.dll MSVCR120.dll

but in the downloaded package, only msvcr110.dll msvcp110.dll are there
So not all the required DLLs are included in the distribution.

I would strongly suggest statically-link to VC runtime when compiling them.
Coordinator
Feb 2, 2015 at 7:52 PM
I didn't originally want to statically link the DLLs to allow updating V8 separately, but given Google's track record of breaking changes, I agree (more reliable anyhow, and guarantees better compatibility within releases).

Thanks for the suggestion/reminder. ;)
Coordinator
Feb 3, 2015 at 7:05 PM
Ok, I've converted V8 to compile V8 statically, and the V8.NET proxy DLLs as well. No more "DLL Hell", lol. ;) It's on the dev branch now.
Marked as answer by jamesnw on 2/3/2015 at 12:05 PM