I tried every workaround I could find. None of it worked.
Is it even possible to get Visual Studio 2008 build tools and v90 in particular for Visual Studio 2017?
What are alternatives? I need this toolset to work on some old code.
Related
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.
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 recently started a new job, and got a machine with Visual Studio 2013 Proffesional installed. This would be great, except the colleague that I'm working with is using Visual Studio 2010. As far as I know, there is no way to work on the same project (or solution), without having quite a lot of issues, is this correct?
And if so, is it still possible to download Visual Studio 2010 (from a reliable source)? I cannot seem to find it anywhere in my MSDN subscriber downloads. All I can find is a stuff like service packs, tools, etc. Did they terminate the support of it?
You work on visual studio 2013 but there are option to select which version of visual studio you want select 2010 and run your project.
You should be able to open Visual Studio 2013 solutions in 2010, if you install Visual Studio 2010 SP1. There is a possibility that some project types won't be supported, but the solution should open.
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.
I want to migrate a Visual Studio 2010 Solution so that I can work with Visual Studio 2013.
If I understand it right, due to the round-tripping feature of Visual Studio 2013,
there is no reason to convert the solution!? I can just open my old solution with
Visual Studio 2013 and can just work with it.
Is that right? Or is there a good reason or need to do a conversion to a
Visual Studio 2013 solution.
Or better: Is there any good reason to not stick with the old Visual Studio 2010 solution?
Visual Studio 2013 can open a sln file created by Visual Studio 2010. However, Visual Studio 2010 can not open a sln file created by Visual Studio 2013.
The easiest way to see this is to open the sln file in a text editor and look at the first 2 lines:
Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio 2012
Visual Studio has a version setting in the header (this example is from VS 2012). An older version of the tool wont open the file.
Beyond that there aren't really any big differences in the file. There are certain project types (ie Project("{guid}") that aren't supported in older version of Visual Studio. For example a Visual Studio 2013 SDK project can only be opened with Visual Studio 2013.
To wrap up, if you have an existing Visual Studio 2010 sln file, there isn't really any need to change it. If you plan on opening it again in VS2010 then make sure you don't change it. Otherwise I wouldn't worry about it and just let VS do whatever makes VS happy.