Thread: MSVCP100.dll

  1. #1
    Registered User
    Join Date
    Jun 2010
    Posts
    6

    MSVCP100.dll

    I'm having strong difficulties in getting a program I wrote with Visual C++ 10 to run on other computers

    I'm either getting an error(when running on a different machine) where it says MSVCR100.dll is missing, or if I put that dll in the folder it says "The procedure entry point "big complicated thing" could not be located in the dynamic link library MSVCR100.dll

    I know that the dll is one that's included in the runtime library of Visual C++, but even when I install that runtime library I get the same error.

    Is there a way I can remove the dependency on the dll by somehow making it compile with the build?

    Thanks, MJHamrick

  2. #2
    C++まいる!Cをこわせ!
    Join Date
    Oct 2007
    Location
    Inside my computer
    Posts
    24,654
    Sounds like you have the wrong dll file?
    Does it help if you install this?
    Quote Originally Posted by Adak View Post
    io.h certainly IS included in some modern compilers. It is no longer part of the standard for C, but it is nevertheless, included in the very latest Pelles C versions.
    Quote Originally Posted by Salem View Post
    You mean it's included as a crutch to help ancient programmers limp along without them having to relearn too much.

    Outside of your DOS world, your header file is meaningless.

  3. #3
    Registered User
    Join Date
    Jan 2008
    Posts
    290
    You don't have to download it. If you have Visual Studio 2010 installed the redistributable packages are located here:

    C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages

    The C++ redistributable is vcredist_x86/vcredist_x64 depending on whether you are using the 64-bit runtime or not.

    Also, I've had issues running debug builds on a non-development machine. I took a guess that the redistributable packages don't install the debug versions of the runtime libraries. This may or may not be true, I have no idea, but in my case the release build runs fine.

    [edit]
    Also you can statically link the runtime libraries by changing your project settings:

    Configuration Properties -> C/C++ -> Code Generation -> Runtime Library

    If you want to statically link the runtime, don't choose one of the DLL options.
    [/edit]
    Last edited by arpsmack; 07-02-2010 at 04:07 PM.

  4. #4
    C++まいる!Cをこわせ!
    Join Date
    Oct 2007
    Location
    Inside my computer
    Posts
    24,654
    It's true that you don't, but it would at least rule out the possibility of bad binaries.
    Also, you are not allowed to redistribute debug binaries, so the installer does naturally not install them. You can't run debug builds on a machine that doesn't have VS installed.
    Quote Originally Posted by Adak View Post
    io.h certainly IS included in some modern compilers. It is no longer part of the standard for C, but it is nevertheless, included in the very latest Pelles C versions.
    Quote Originally Posted by Salem View Post
    You mean it's included as a crutch to help ancient programmers limp along without them having to relearn too much.

    Outside of your DOS world, your header file is meaningless.

  5. #5
    Registered User
    Join Date
    Jan 2008
    Posts
    290
    Also, you are not allowed to redistribute debug binaries, so the installer does naturally not install them.
    Thank god. I searched MSDN for verification, but sometimes I feel that I would get answers faster if I just pounded my face on my keyboard for a while. It amazes me that Google is better at searching MSDN than MSDN is.

    I did continue searching after reading your post and eventually found an MSDN article that explains the issue: Preparing a Test Machine To Run a Debug Executable It was conveniently nested under the "Deployment Examples" category.

Popular pages Recent additions subscribe to a feed