I have developed an application with Visual Studio 2012. I have also created a setup.exe with Install Shield 2010 Premium for my application. My development environment is Windows 8 64-bit, the application is compiled under Release Win32. The developing language is C++.
After building setup.exe, I ran it on another computer that is running on Windows 7 64-bit. An error message box pops up saying MSVCP110.dll is missing or not configured to run on Windows. Any ideas as to why this may be?
I tried installing Visual C++ Redistributable for Visual Studio 2012 (http://www.microsoft.com/en-au/download/details.aspx?id=30679), but it still gives the same error.
Any help would be appreciated.
MSVCP110.dll is really part of VC++ Redistributable package.
Try to install both versions of them: x86 and x64 if your machine is 64 bit.
For 32bit machine you need only x86 package.
Related
I've installed easyphp-devserver on windows 10. When I launch easyphp, the message "msvcr110.dll is missing" appears.
I've searched on internet and found out I must install the Redistribuable Visual C++ for Visual Studio 2015 [https://www.microsoft.com/en-us/download/details.aspx?id=48145][1]
After that, I installed Visual C++ and reboot my computer.
But that doesn"t work. There is the same error message.
Have you any idea to solve the problem ?
I assume you're referring to the Windows 7/8/10 VC14 version with PHP 7 support (v16.1.1 at the time of this post).
The EasyPHP Devserver download page states that Visual C++ Redistributable for Visual Studio 2015 x86 or x64 is required, which should come installed on Windows 10 already.
What it doesn't mention is that apparently Visual C++ Redistributable for Visual Studio 2012 is also required, and doesn't come installed on Windows 10. Here's the download link for that one:
https://www.microsoft.com/en-us/download/details.aspx?id=30679
Installing the x86 executable got it working for me. No need for the x64 one it seems.
As highlighted by Adam C try downloading the 32bit (e.g. x86) version of Visual C++ Redistributable for Visual Studio 2012 it should resolve the issue... as I had the 64bit Win7 installed I tried to use the 64bit Redistributable file and it did not help fix the issue... but, used the 32bit version and vola it worked.
Unable to start MongoDB 3.0.9,3.1.9,3.2.0,3.2.1 after installation on Windows 2012 R2 after installation. Continually receive APPCRASH errors. MSVCR120.dll c000001d.
Builds 2.7.9 and 3.0.0 do not experience the same issue.
You can resolve the issue by installing the 64 bit (or 32 bit) version of the Visual C++ Redistributable Packages for Visual Studio 2013. It can be downloaded from Microsoft:
https://www.microsoft.com/en-us/download/details.aspx?id=40784
When I installed Microsoft Visual C++ and C# 2008 Express, I got "Microsoft Windows SDK for Windows Server 2008" added in.
I want to know if I can remove it and still have all the functionality of Visual C++/C#.
Strange, I remember it was shipped with Vista RTM headers (The Microsoft Windows Software Development Kit Update for Windows Vista version). Looks like Microsoft updated the SDK bundled with Express.
Anyway, the SDK is responsible for a lot of features in Visual Studio. For example, Visual Studio invokes sgen.exe to generate XML serializer assemblies, and call rc.exe to compile a resource script. Chances are you can't get away without it if you are not writing hello-world apps.
I can't run a debug sdk application because it requires both VC 8 and VC 9 versions of the CRT. But it only requires visual studio 2008 for plugin dev, which is what I need.
How do I install the debug runtimes from 2005 on to a Windows7 machine? I can't figure out how to make them run app local nor can I copy anything into the winSxS folder without a trusted installer.
Refer to this post.
As per this the debug dlls can be found at:
For Visual Studio 2005:
C:\Program Files\Microsoft Visual
Studio 8\VC\redist\Debug_NonRedist\x86
For Visual Studio 2008:
C:\Program Files\Microsoft Visual
Studio
9.0\VC\redist\Debug_NonRedist\x86
Also as per what I know you need not have these dlls in the WinSxS folder. Even if these dlls are present in the same directory as your application exe is, it will do.
Anyways using debug dlls in production environment is not recommended.
In case you elevate your application, make sure you set the 'Start in' path to the application home/install directory or add the path to the VC++ debug dlls to the PATH environment variable.
You must install visual studio to get the debug CRT. This will be moot as soon as we don't need 2005 or 2008 again.
You can create a simple setup project (vdproj) which pulls in the debug merge modules.
This works fine up to Visual Studio 2010 (VS10) but is not supported for 2012 (VS11) and later :o(
You must install the C++ compilers to get the debug CRT, but you don't have to install all of Visual Studio. Instead, use the web install of the Windows SDK to install the compilers. The Windows 6 SDK includes the VC8 compilers, the Windows 7 SDK includes the VC9 compilers and the Windows 7.1 SDK includes the VC10 compilers.
I am trying to run NUnit in Visual Studio 2003 on 64-bit Vista but with no success.
I have set the Debug Mode of the Project to "Program" and the Start Application to "C:\Program Files (x86)\NUnit 2.4.8\bin\nunit.exe". The Test Project is set as the StartUp Project. All the code is in .NET 1.1. Unlike .NET 2.0 the processor architecture cannot be targeted (when a 1.1 executable is loaded on an x64 machine it is run in the WoW64 as a 32-bit process and utilises the 32-bit framework).
After I hit Debug > Start I receive the error window "A project with an Output Type of Class Library cannot be started directly". I am stuck and cannot get NUnit to run.
The nearest related question on stackoverflow dealt with getting NUnit to run on Vista x64 in Visual Studio 2005 "Nunit.exe cannot work on Vista 64bits if x86 build (stackoverflow.com/questions/208985/nunit-exe-cannot-work-on-vista-64bits-if-x86-build).
Additionally NUnit did not install a nunit-x86.exe from the NUnit-2.4.8-net-1.1.msi image.
My Development Environment
Vista x64 with SP1
Visual Studio 2003 (version 7.1.3088)
.NET Framework 1.1 (version 1.1.4322 SP1)
NUint 2.4.8 (installed from NUnit-2.4.8-net-1.1.msi)
I found the issue - and it had nothing to do with Vista x64.
I had set the Debug Mode of the main Project to "Program" and the Start Application to "C:\Program Files (x86)\NUnit 2.4.8\bin\nunit.exe" and not the Test Project.
Even though I had set the Test Project to the StartUp Project the Debug Mode in the Test Project was still set to the default "Project" and not to the "Application". I switched the debugging configurations around; so the main Project was set to "Project" and the Test Project contained the NUnit debugging configurations.
Summary: NUnit does run on Vista x64 in Visual Studio 2003.
IF your app is a 32-bit app, then you have to use nunit-x86.exe, it is built for testing a 32-bit application on a 64-bit system. See detail explanation here: http://www.nunit.org/index.php?p=nunit-gui&r=2.4.2