Direct link to VC++ 2010 SP1 Redistributable from custom installer - visual-c++

I have installer that contains vcredist_x86.exe / vcredist_x64.exe so if user machine does not have VC++ redistributable installed then I install it.
However, the size of vcredist_x86.exe / vcredist_x64.exe is quite large ~5MB, which may be a problem for a small application.
Is there a direct (and permanent) link to Microsoft site that I could use instead of adding vcredist files to my installer?
Or may be there is even better way to solve such problem?
P.S. I am aware that user machine would have to be online - this is OK.

Here are the direct links for MSVC 2010 redists:
MSVC 2010 SP1 Redist x86 English
http://download.microsoft.com/download/C/6/D/C6D0FD4E-9E53-4897-9B91-836EBA2AACD3/vcredist_x86.exe
MSVC 2010 SP1 Redist x64 English
http://download.microsoft.com/download/A/8/0/A80747C3-41BD-45DF-B505-E9710D2744E0/vcredist_x64.exe
As you can see from those URLs, Microsoft is using UUIDs to index all their downloads, which looks like a good design decision and suggests that those links are indeed going to remain valid for a long time.

Microsoft Visual C++ 2010 SP1 Redistributable Package (x86)
Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)

Related

Visual C++ Redistributable 2013 (vcredist for 2013) platform support for Windows 2016

As per the information published for Microsoft Visual C++ Redistributable 2013, Windows 2012 R2 is the latest platform supported on Windows Operating systems.
Our application code (C++) is built with Visual Studio C++ 2013 and we are using VC++ redistributable 2013 on Windows 2012 R2 platform to work with the binaries which are built as mentioned above.
Now, we are planning to use VC++ redistributable 2013 on Windows 2016 platform to work with same binaries. When I check for platform support of VC++ redistributable 2013 for Windows platforms, Windows 2012 R2 is the latest platform supported and I dont see Windows 2016 is mentioned in the supported platforms list. (Ref: https://msdn.microsoft.com/en-us/library/ms235435(v=vs.120).aspx)
When I test internally with VC++ redistrbutable 2013 on Windows 2016 platform, binaries are running good as expected as of now.
So, I am assuming VC++ redistrbutable 2013 supports on Windows 2016 platform.
Can you please provide confirmation on support of VC++ redistrbutable 2013 supports on Windows 2016 platform? So that, we can use our application on Windows 2016 platform using VC++ redistrbutable 2013.
If these are any published KBs for support of VC++ redistrbutable 2013 on Windows 2016 platform, Please share.
Please provide confirmation on support of VC++ redistrbutable 2013 on Windows 2016 platform.
If I understand the table you link to correctly, it specifies for which platforms you can build software for with the given Visual Studio version. This does in no way imply that the software so built does not run on more modern platforms.
Typically, the opposite will be the case: Old software will run on modern platforms. That's called compatibility. I do not think that Microsoft will decide to break (moderately) old software wholesale and intentionally.

Which Redistributable Package for MSVC 2013? there are multiple

I am a bit confused with which version of the MSVC Redistributables for Visual Studio 2013 I need to include with my installer when people install my application.
I have been including and auto-installing what I thought was the correct vcredist_x64.exe, but upon installation on a brand new Win10 box, it needed a different vcredist_x64.exe.
How do I know which is the correct redistributable for my developed-with-visual-studio-2013 application when there are multiple versions of the x64 vcredist_x64.exe?
I also noticed that there is "update 5" for visual studio 2013 - if I install this update, does that change the redistributable I need to include in my installer?
This is the official page where you can download the latest redistributable: Visual C++ Redistributable Packages for Visual Studio 2013. There is also Redist directory with appropriate installers somewhere inside Visual Studio 2013 installation directory.
It is possible that you had redist for older version of VS2013 that you used for building your application.

WDK + Windows 8 + MSVC 2010

ALL,
I would like to build a dokan library. According to dokan instruction I need the WDK which can be downloaded from the Microsoft website.
Problem is - I have MSVC 2010 and it looks like WDK is for MSVC 2013 and I don't know what to do.
Could someone explain to me where can I get WDK for MSVC 2010?
Thank you.
The Windows 8.x SDK generally works with Visual Studio 2010--with the exception of a few places in the include\winrt headers where they used C++11 constructs not supported prior to VS 2012, specifically strongly-typed enumerations. The issue is there is no automatic integration for the VS 2010 toolset.
The recommended solution is to use .props files. See the Visual C++ Team Blog for details, and I have the fully authored .props files for both x86 and x64 hosted on my blog. These are also used in my open-source projects (DirectX Tool Kit, DirectXTex, DirectXMesh, UVAtlas, DXUT, Effects 11) which support VS 2010 + the Windows 8.1 SDK.
I believe the situation is basically the same with the Windows Driver Kit 8.x as it actually integrates into the existing Windows 8.x SDK. You will just need to add include\km and lib\km folders to the .props for the kernel mode projects.
That said, with VS 2013 Community edition being freely available full-featured version of Visual Studio under generous license terms, I'm not sure why you are sticking with VS 2010...

Can we install VC++ 2015 Redistributable Package in custom location, where as non-administrator has rights to access?

We have VC++ projects in VS 2008 and Wpf Projects in 2010. We want to migrate both of them to Visual Studio 2015.
The biggest problem we face, while a new user needed to install our software is, he need to install the pre-requisite of installing VC++ Redistributable Package, which requires Administrator rights. Then he need to install our application via clickonce server.
We want to ease this part - installing VC++ Redistributable Package.
Is the new 2015 VC++ Redistributable can be installed in my application path, without requiring administrator rights? I could not the spot the link to download VS 2015 VC++ R P link - please provide.
I got the suggestion of using /MT (linking statically) from below link, but we want the application to be statble (as we also dispatch patches), we don't want a library conflict.
https://social.msdn.microsoft.com/Forums/vstudio/en-US/a8d4ca59-c295-43bf-b34e-518fe2f7977c/vc-2015-redistributable-package?forum=vclanguage#667db896-f517-4fa5-b5b7-b5b0c3d12d52
Please, help.
I believe no, you can't do that.
Read this article at VC++ team blog: Introducing the Universal CRT, where James McNellis said:
App-local deployment of the Universal CRT is not supported.

Can an application built with VC++ 2010 run reliably with just the VC++ 2013 redistributable installed?

So here is my situation: We have some applications built using VC++ 2010, but others are now built with VC++ 2013.
In the past, when setting up a client machine, only VC++ 2010 Redistributable was installed, but with the development of some of these applications now in VC++ 2013 we need to install the VC++ 2013 Redistributable.
I know that the Redistributable packages are installed side by side and that applications developed in VC++ 2010 will go to their appropriate file set if it exists on the machine.
But can a VC++ 2010 project run reliably with just the VC++ 2013 redistributable installed?
This question occurred to be when I saw that Microsoft named the VC++ 2010 and 2013 redistributable install files the same. For example, vcredist_x86.exe.
Thanks for your time!
No, your VS2010 built app will need msvcr100.dll (etcetera), the VS2013 installer will deploy msvcr120.dll
Doing anything to force VS2010 to use the VS2013 runtime library is very unlikely to turn out well. The new C++11 language standard has caused lots of upheaval in the runtime libraries. The good kind of upheaval, but not exactly very compatible with old compilers.
You must therefore install the VS2010 runtime libraries as well.

Resources