Visual Studio 2015 Update 2 has been released for 7 days. Where can I download the Visual C++ Update 2 runtime so I can run the applications compiled with Visual C++ 2015 Update 2?
Here is the download
Microsoft Visual C++ 2015 Redistributable installs run-time components
of Visual C++ libraries. These components are required to run C++
applications that are developed using Visual Studio 2015 Update 3 and
link dynamically to Visual C++ libraries. The packages can be used to
run such applications on a computer even if it does not have Visual
Studio 2015 installed. These packages also install run-time components
of C Runtime (CRT), Standard C++, MFC, C++ AMP, and OpenMP libraries.
Microsoft Visual C++ 2015 Redistributable includes bug fixes to the
runtime DLLs and also the latest versions for KB 2999226.
There are two files in the Visual Studio 2015 Update 2 VC++ Redistributable package.
vc_redist.x64.exe (v14.0.23918.0).
https://download.microsoft.com/download/0/5/0/0504B211-6090-48B1-8DEE-3FF879C29968/vc_redist.x64.exe
vc_redist.x86.exe (v14.0.23918.0).
https://download.microsoft.com/download/0/5/0/0504B211-6090-48B1-8DEE-3FF879C29968/vc_redist.x86.exe
For those that care, the x64 version sets the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DevDiv\VC\Servicing\14.0\RuntimeMinimum\UpdateVersion (REG_SZ) to the value "14.0.23918".
For the x86 version, check for the existence of the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall{2e085fd2-a3e4-4b39-8e10-6b8d35f55244} If it exists, the update is already installed.
Related
I am going to compile old project(visual studio 2012 platform-v110xp) in visual studio 2013 or Visual Studio 2019.
It's using boost and Microsoft detour 3.0 libraries.
But the detour 3.0 has been deleted accidentally.
And now I can only find detour4.0.
But I get an error like this
How do I get the detour 3.0 lib?
C++ Static Libraries built with VS 2015, VS 2017, or VS 2019 are "binary compatible", but that's not true of any other versions of Visual C++. For example, a static library that links with VS 2012 won't necessarily work when linked with VS 2013 code. See Microsoft Docs.
I don't know exactly what toolsets are involved but that's the likely cause of the link issues. The main thing is to make sure all the static libraries and main executable is built by the same compiler version.
Note that DLLs and their export libraries typically use only "C-style" binding so they can be binary compatible with multiple generations of compilers.
VS 2019 includes the v141_xp platform toolset (i.e. the VS 2017 compiler using the Windows 7.1A SDK that is compatible with Windows XP / Windows Server 2003).
From what I read about these posting and elsewhere, regarding the issue of why I cannot install Microsoft VC++ 2015 runtime redistributable if I already have Microsoft VC++ 2017 runtime installed.
The reason for this "cannot install" is because once you have Microsoft VC++ 2017 installed, there is no need to install 2015 version,as 2017 subsume 2015. Am I right?
Secondly, and more crucially, from now onwards if I have a higher version of Microsoft VC++ installed, I can safely skip the lower version, this is going to be Microsoft strategy: going forward there is only one version of Microsoft VC++ ( the latest one). Am I right? I remember I read this elsewhere, but not sure my understanding is correct or not, and now I couldn't find the blog post. So I hope that I can get some confirmation here.
The VC++ runtime redistributables are the same for VS 2015, 2017 and 2019! From Microsoft Support:
Note Visual C++ 2015, 2017 and 2019 all share the same redistributable files.
However, there have been many different versions of this redistributable package released! The installer programs (linked below) will do the required checks, to see if a more recent version is already present on the target computer, and signal if so.
The runtime libraries that comprise this redistributable package are sometimes (confusingly) referred to as Visual C++ "14" Runtime Libraries. (The "14" comes from the fact the Visual Studio 2015 includes version 14 of the MSVC compiler; VS2017 = MSVC v15; and VS2019 = MSVC v16.)
Whether or not future versions of Visual C++ will also share the same redistributable package is not certain.
The latest versions, for the three supported processor platforms, can be downloaded and/or installed from the following links:
x86 - vc_redist.x86.exe
x64 - vc_redist.x64.exe
arm64 - vc_redist.arm64.exe
EDIT: There may be some confusion, here, over the 'version check' I mentioned above! From the same Microsoft Support page:
For example, installing the Visual C++ 2019 redistributable will
affect programs built with Visual C++ 2015 and 2017 also. However,
installing the Visual C++ 2015 redistributable will not replace the
newer versions of the files installed by the Visual C++ 2017 and 2019
redistributables. This is different from all previous Visual C++
versions, as they each had their own distinct runtime files, not
shared with other versions.
I interpret this as meaning that, if you have an 'older' version of the vc_redist installation (released, say, with VS2015), it's components will be updated by any newer installation. However, running an older installer will not conflict with a more recent installation.
I've installed Visual Studio 2010 Express but I need the x64 compiler toolset. I can not install the compiler toolset with the Windows 7.1 SDK on my Windows 10 machine, it says ".NET Framework 4 is not installed".
How can I get the x64 compilers of Visual Studio 2010?
For me it worked with the following steps (older Visual Studio version can be downloaded through https://www.visualstudio.com/vs/older-downloads/ (required login))
Install Microsoft Visual Studio 2010 Express (en_visual_studio_2010_vc_express_web_installer_x86_516528)
Install Microsoft Visual Studio 2010 SP1 (mu_visual_studio_2010_sp1_web_installer_x86_651694)
Install Microsoft SDK (from https://www.microsoft.com/en-us/download/details.aspx?id=8279). Note that when running the installer a warning will appear saying that "some components cannot be installed". Just ignore this (press OK) and continue with the installation using the default settings. Note that the 64-bit C++ compiler is not installed at this point.
Install KB2519277 (from https://www.microsoft.com/en-us/download/details.aspx%3Fid=4422).
Both the 32- and 64-bit Visual Studio 2010 C++ compilers should now be installed.
Note that I'm not sure if all the above steps are actually necessary and if the order is strictly relevant (e.g. it might also work without installing SP1 or installing SP1 later) but this is what worked for me.
I found an installer for VS 2010 Professional on CNet: http://download.cnet.com/Microsoft-Visual-Studio-2010-Professional/3000-2212_4-10618634.html It installed the x64 compilers as well.
I install visual studio 2013 ultimate on a x64, and i get with is components from 2005 and a whole bunch for x86 ?!
Microsoft Visual C++ 2005 redistributable x86
It also , if i am not mistaken, gives me a version of visual studio 2010 as well as tooling and files only associated for those versions. There was no option to negate this. Do i really need all of this?
Are there many redistributable packages? If so, how do I know which package to download?
You will need the redistributables for any of the environments you develop in. Note the "full" versions for the .net Frameworks contain both 32-bit and 64-bit versions.
http://msdn.microsoft.com/en-us/library/5a4x27ek.aspx
You can select other versions (.net 3.5, etc) from the "Other versions" link at the top of the page.
For C++, the VC2010 redistributables are here:
x86 - http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a7b7a05e-6de6-4d3a-a423-37bf0912db84
x64 - http://www.microsoft.com/downloads/en/details.aspx?FamilyID=BD512D9E-43C8-4655-81BF-9350143D5867
The visual studio SP1 redistributable fixes issues (bugs) in visual studio and updates the security
-> Use this if you have VS and want to update
The visual studio redistributable puts updated versions of assemblies, packages and dlls on your machine
-> Use these if you have programs that depend on the updated packages
If using InstallShield, you should update your MSMs to point to the new Visual C++ libraries.