The second option doesn’t really make sense to me and I would probably never do it. The first option seems the most stable and robust and easiest for a single executable. Forced everyone to install the VC++ Runtime Redistributable before running the app.Included the dll in the same directory as the exe (I actually didn’t try this but I assume it would work).Statically link to the dll files so they are compiled into my executable instead of referenced as separate dll files.You can solve this any of the following ways: It was actually really easy to resolve for my one project. It seems like this should just not happen by default, but unfortunately it does. I create a new project in Visual Studio 2010 using the project type of C++ Win32 Project and without making a single change to the default project, I built the file and tested it on my clean machine and the same issue occurred. The screen shot is identical except for the D in the dll name.
The same things happens with the debug version of the file, only it is a the debug version of the same DLL as noted by the fact that the DLL name ends with D. Try reinstalling the program to fix this problem. The program can’t start because MSVCR100.dll is missing from your computer. Once I compiled it with Visual Studio 2010 and ran it on a clean 2008 server (fully patched but otherwise clean), it failed to run with the following error. I had a C++ application that worked perfectly in Visual Studio 2008. Ok, so recently I switched to Visual Studio 2010. This file has debugging enabled and is not considered redistributable. The MSVCR100D.dll is almost the exact same file only the D at the end stands for Debug. If you create a C++ project in Visual Studio 2010, this file is probably needed. This msvcp100.dll is the Microsoft Visual C++ Redistributable dll that is needed for projects built with Visual Studio 2010.
This msvcr100.dll is the Microsoft Visual C++ Redistributable dll that is needed for projects built with Visual Studio 2010.
0 kommentar(er)
