Is it possible to apply fixes on Visual C++ Build Tools 2015 Update 3 - c++

Visual Studio 2015u3 is serviced by cumulative updates with KB3165756, which contains, among other things, fixes to the C++ compiler and libraries.
However KB3165756 refuses to do anything on a computer where Visual C++ Build Tools 2015 Update 3 is installed. It really wants one of VS Pro, Enterprise, Community or Express.
Are there special patches for Visual C++ Build Tools, or is it not updated at all and so it is actually a better idea to switch to Visual Studio Express 2015 for Desktop, in order to be able to receive patches?

Here is the answer I got on MSDN Visual Studio Development > Visual Studio Setup and Installation forum:
However KB3165756 refuses to do anything on a computer where Visual C++ Build Tools 2015 Update 3 is installed. It really wants one of VS Pro, Enterprise, Community or Express.
It is reasonable, check this: https://msdn.microsoft.com/en-us/library/mt752379.aspx and it describes this update is applies to
Visual Studio Professional 2015
Visual Studio Enterprise 2015
Visual Studio Community 2015
Visual Studio Express 2015 for Web
Visual Studio Express 2015 for Desktop
Visual Studio Express 2015 for Windows 10
I have researched around and it looks like there is no special update for the Visual C++ Build Tools 2015, and refer to this blog: https://blogs.msdn.microsoft.com/vcblog/2015/11/02/announcing-visual-c-build-tools-2015-standalone-c-tools-for-build-environments/
The latest release of the Visual C++ Build Tools 2015 is here: Download Visual C++ Build Tools 2015
If you still want to install, it looks like you need a VS 2015 RTM update version on your computer. Since the VS community 2015 with update 2 and Visual Studio Express version are free and you can think about it.
Best regards,
Sara

Related

Compiling using MSBuild 12.0 from Microsoft Visual Studio 2015

I have a solution that was compiled with MSVC 12.0 Visual Studio 2013 (C++/CLI and C#) but only have Visual Studio 2015 (Community). I want to build the project using MSVC 12.0 as it was intended, as I only need to rebuild 1 part of the solution (of 5) for my purpose and want it to be compatible with the other DLLs. When trying to build it from MSVC 14.0 (Visual Studio 2015) it says:
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Platform.targets(57,5): error MSB8020: The build tools for v120 (Platform Toolset = 'v120') cannot be found.
Of course I installed the MS Build tools for 2013 (MSVC 12.0, v120) from here: https://www.microsoft.com/en-us/download/details.aspx?id=40760 as well as the Microsoft Visual C++ Redistributable 2013 package.
And the right directory for the 12.0 build tools install is C:\Program Files (x86)\MSBuild\12.0\Bin\amd64
It looks like a configuration error on the solution (or in Visual Studio in general) since it is looking for the build tools in the wrong directory. Does anyone know what settings I need to change / add in Visual Studio to get it to compile with MSBuild 12.0 instead of 14.0? I'd prefer not to install Visual Studio 2013 since I don't use it for anything else (just want to have the option to use VS 2013 MSBUILD within VS 2015 as needed).
Okay I have gotten this working although in a roundabout way. Thanks others that have answered and commented. Sign up for a Microsoft Visual Studio Dev Essentials subscription for free. https://azure.microsoft.com/en-us/pricing/member-offers/vs-dev-essentials/ Then you can go through the menus and download Visual Studio Community 2013 by going to this link and finding it https://my.visualstudio.com/downloads. After doing so, you can build MSVC 12.0 from Visual Studio 2015. Sure, not perfect, but it works. I haven't tried uninstalling Visual Studio 2013 to see if it still works (Windows Phone SDK 8.1 is installed with 2013 as was mentioned to get it working in the Enterprise version of 2015) but if you could somehow keep that and remove the 2013 edition I believe it could work without 2013 installed...
If you go to the top of your .vcxproj change it to this
<Project DefaultTargets="Build" ToolsVersion="12.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
Then your .sln can still open in Visual Studio 2015
VisualStudioVersion = 14.0.25420.1
The reason is because the compiler version is specified on a project-by-project basis, and will override the solution version.
I'd prefer not to install Visual Studio 2013 since I don't use it for anything else (just want to have the option to use VS 2013 MSBUILD within VS 2015 as needed).
You can install VS2013 toolset version from your VS2015 installer without installing visual studio 2013. From the 2015 installer, select Windows 8.1 and Windows Phone 8.0/8.1 Tools and common Tools for Visual C++ 2015:
After installation completed, you will find the platform Toolset below:
Then you can built your project with platform toolset Visual Studio 2013(v120).
You can refer to more info from the similar question on SO.

Intel parallel studio 2017 is integrated in visual studio 2013, now how to integrate it to visual studio 2015

I installed visual studio 2013 ultimate, then intel parallel studio 2017 cluster edition and the latter was integrated in visual studio 2013 (access, through visual studio menus, properties etc, to intel functionalities, c++ compiler etc). Maily to use the c++ mkl library.
Now, I installed visual studio 2015 enterprise, and I would like my intel parallel studio 2017 cluster edition to be integrated to it.
I relaunched the setup.exe of intel parallel studio 2017 cluster edition and saw no option allowing me to achieve this. I even repaired (it's an option in the installer) my intel parallel studio 2017 cluster edition installation, without success.
I could do a complete remove and a reinstall, but I'd rather avoid doing this. How could I proceed ?
One should not use setup.exe in parallel studio 2017, but rather w_mkl_2017.0.109_online.exe installer, which indeed allows to "Choose Integration Target", with options to integrate all available and integrable visual studios. (While seteup.exe doesn't.)

Share project between Visual Studio 2013 and Visual Studio 2012

I am using Visual Studio 2013 community and created C++ project.
I want to share the project with a colleague working with Visual Studio 2012 professional.
Once he took the project he had to change the toolset to v110 and it worked just fine for him.
When he shared it back with me I got the message:
error MSB8020: The build tools for Visual Studio 2012 (Platform Toolset = 'v110') cannot be found.
To build using the v110 build tools, please install Visual Studio 2012 build tools.
Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Upgrade Solution...".
I do not want to upgrade the solution, as that will cause us each time to change the project, but I couldn't find anywhere to download the VS2012 build tools.
Where can I find Visual Studio 2012 build tools?
You can have both Visual Studio 2012 and Visual Studio 2013 installed on the same machine. Once you have both installed you can use the Visual Studio 2012 compiler in Visual Studio 2013.
So I suggest you install Visual Studio 2012. I think Express edition should be enough.
Alternatively, your colleague can install Visual Studio 2013 Community Edition alongside his existing Visual Studio 2012 Professional Edition. I think the features are roughly equivalent the only question is if they are breaking the license terms.

Remote debugging on Surface Pro 3

I've installed x64 version of remote debugging components for Visual Studio 2015 on my Surface Pro 3 with Intel Core i3 CPU and recently updated to Windows 10 Pro Insider Preview x64.
When I'm trying to debug remotely simple universal application from Visual Studio 2015 RC (development machine runs Windows 8.1 Pro) I'm having this error in the output window:
Error: Unable to connect to the Microsoft Visual Studio Remote Debugger named '192.168.1.2:4020 (hosthame)'. The remote debugger is older than this version of Visual Studio 2015 RC, and Visual Studio is no longer compatible with it. Please upgrade your remote debugger to match Visual Studio.
Also there are records of failed attempt to connect in the main (log) window of Remote Debugging Monitor.
So, is there any "more updated" version of remove debugger component for Visual Studio 2015 RC then the current one I'm using, which, btw, has version 14.0.22310.1 and was "built by: DP" (have no idea what does it mean)?
Or any thoughts about other ways to workaround this issue?
I'm looking into installing Visual Studio on the Surface directly, but would like to avoid it if possible.
OK, I'll google next time harder - Remote Tools for Visual Studio 2015 RC (this link is no longer available, please use the links bellow).
Update (2016-06-28)
Remote Tools for Visual Studio 2015 Update 3:
Download (this link is no longer available, please use the links bellow)
Update (2016-09-28)
x64 - Remote Tools for Visual Studio 2015 Update 3
x86 - Remote Tools for Visual Studio 2015 Update 3
ARM - Remote Tools for Visual Studio 2015
Sevenate, your latest link is for the 2013 and not the 2015. Your second link still works, people just have to go to:
Tools for Visual Studio 2015->Remote Tools for Visual Studio 2015 and download the one for Update 3. I hope this helps

How to install one version of visual studio 2013 with c++ 2010, 2012 and 2013 toolsets

How can I install visual studio 2013 with c++ 2010, 2012 and 2013 toolsets without installing any other visual studio versions (express or any other versions).
I need this so that I can keep my pc light and clean. Are there any alternatives to installing multiple visual studio versions for c++ toolsets?
I am developing a plugin for a program that has multiple version each compiled in c++ 2010 and c++ 2012 so I need those version of c++ toolset. For daily use I need visual studio 2013.
In the end I installed the express editions that use around 800mb each and do not add so much clutter.
MSDN's website says that if you want the C++ 2010 and C++ 2012 toolsets with VS2013, you'll need to install those VS versions on that particular machine. Link here
I don't think there are other alternatives to that.