I am trying to build boost, I have both visual studio 2005 and visual studio 2010 installed on my machine when I ran bootstrap.bat it by default taken visual studio 2010. How do I force this to build with visual studio 2005
On bjam (or b2) command-line try adding the following "toolset=msvc-8.0"
Related
Project on what I must work need platform Visual Studio 2010 (v100) platform toolset but in Visual Installer I don't see this. How can I install this to VS 2019?
I am trying to build a VS 2017 solution which includes a Visual Studio Installer Project with the just released Visual Studio Pro 2019. Of course, when I tried to open the solution I got an error because there was not Visual Studio Installer project type in VS 2019. And, I cant find a place to load it from.
How do I add a Visual Studio Installer Project type in the released version of VS 2019?
Install the addin in Visual Studio 2019:
This extension provides the same functionality that currently exists
in Visual Studio 2015 for Visual Studio Installer projects. To use
this extension, you can either open the Extensions and Updates dialog,
select the online node, and search for "Visual Studio Installer
Projects Extension," or you can download directly from this page.
This extension is designed to work with Visual Studio 2017 and
Visual Studio 2019.
I need MSBUILD 14.0 and am willing to install Visual Studio to get it.
What version of Visual Studio do I need to install to get MSBUILD 14.0?
It looks like the MSBUILD version number and the Visual Studio name do not match.
Starting in Visual Studio 2013, the MSBuild Toolset version is the same as the Visual Studio version number. So if you have Visual Studio 2015 you should have MSBuild 14.0 already on your system.
We have a buildmachine that currently has installed Visual Studio 2010 to compile our application.
Now we have moved to Visual Studio 2015 and developers have installed it on their machines and modified the solution so it works with 2015 but the previous versions will continue to build with 2010.
I was going to install Visual Studio 2015 on the build machine but I don't know how the build machine will know that the previous branches must be built with 2010 and the new ones with 2015. With some Msbuild settings? Just looking at the sln? By other means?
With some Msbuild settings? Just looking at the sln? By other means?
Open your .sln file with Notepad. Look for Format Version on the first line which correlates with a Visual Studio version.
•Format Version 11.00 is Visual Studio 2010
•Format Version 12.00 is Visual Studio 2013 && Visual Studio 2013
For visual studio 2013 and visual studio 2015, we could find the visual studio version on the third line. like this:
visual studio 2013: VisualStudioVersion = 12.0.30501.0
visual studio 2015: VisualStudioVersion = 14.0.25420.1
As far as I know it does it looking at the ToolsVersion on every .csproj. VisualStudio is not required as MsBuild and the compiler come with the .Net Framework.
I have been using 2010 on a project. The project was built using cmake, when cmake chose to use the compiler Visual Studio 2010. Now I intend to move the whole set up of the project to Visual Studio 2013.
So, today I installed Visual Studio 2013. But when I try to use cmake to build the project for visual studio 2013, in the compiler list of cmake I cannot see any compiler of Visual studio 2013, the latest are Visual Studio 2012, Visual Studio 2012 win64, Visual Studio 2012 ARM.
Is there no exclusive compiler for Visual Studio 2013? Does the same compiler work for both VS2012 and VS2013? If Visual Studio 2013 indeed has an exclusive compiler, why can't cmake find the that compiler?
Thanks.
Try updating your CMake version.
The Configue dialog in cmake-gui for CMake 3.1 lists the respective entries as Visual Studio 12 2013:
In older CMake versions (older than 3.0) the entries omitted the year and showed only the version number, so the entry just reads Visual Studio 12.
If your CMake version is even older, there might not be support for Visual Studio 2013 at all. However, you should still be able to open project files generated for an older Visual Studio version. This might require an additional conversion step by Visual Studio, which might mess things up.
Upgrading CMake is definitely the preferred solution.