MSVCP120D.dll is missing when running SampleVS2012

#1

I tried running the samples and I get this error in Visual Studio 2012.
Checked the folders, MSVCP120D.dll is already there. Could somebody help me sort this out?

#2

It looks like SampleVS2012.vcxproj is missing something. For Visual Studio 2008, we have this explicit copy :

  <Tool
    Name="VCPostBuildEventTool"
    CommandLine="copy ..\lib\x86\Leapd.dll "$(OutDir)"
copy ..\lib\x86\msvcr120d.dll "$(OutDir)"
copy ..\lib\x86\msvcp120d.dll "$(OutDir)""
  />

We already knew there was a bug in SampleVS2010, but I also can't find the corresponding commands for SampleVS2012.

msvcr120d.dll and msvcp120d.dll exist in the SDK, but did you try explicitly copying them to your Debug output folder (adjacent to Sample.exe)? (Note that the Release x86 configuration should be fine, because the Core Services installs the Visual C++ 2013 redistributable).

If it still fails in that case, you can download and run Dependency Walker on Sample.exe.

#3

I tried copying it into the Debug folder, but I get the same error frowning
Any help appreciated !

#4

I also ran into the same error:

I was able to copy the DLLs manually into the system32 folder but now when the application runs it throws an error that says:

Sample.exe - Entry Point Not Found
The procedure entry point except 1 could not be located in the dynamic link library MSVCR120D.dll

Doing some googling/poking around this means that one of the dependencies is still building against the wrong version of visual studio or something. I haven't figured out what to do from here.

//Just as a note. You can avoid the issue by building the release version of the application.

#5

Copy both files in your Debug folder:

  • msvcp120d.dll
  • msvcr120d.dll

Then it worked for me.

#6

Here are my screen shots, I followd as you've suggested --_


Any help, I couldn't get started with this unfortunately frowning

The images don't show up for some reason, please click on the broken images, they are loading fine.

#7

0xc000007b typically means you're mixing a 32-bit application with a 64-bit DLL. If building the Win32 configuration, be sure to use LeapSDK\lib\x86, not LeapSDK\lib\x64.

Come to think of it :

I was able to copy the DLLs manually into the system32 folder

Which DLLs did you copy into there? Note that on 64-bit Windows, only 64-bit DLLs should go into C:\Windows\System32. Ironically the folder for 32-bit DLLs is C:\Windows\SysWow64.

#8

Thanks jdonald, that works smile
I copied the 32bit version of dll into the Debug folder of the Sample.