I want to upgrade from Visual Studio 2017 to Visual Studio 2019. Does anyone know a method to not lose my projects and settings?
You don't lose any files. your projects are saved on your computer not on a VS2017.
When you go and upgrade to Visual Studio 2019, you won't lose your files, it does it all for you.
Related
My laptop has Windows 7 64-bit operating system. I have both Visual Studio Community 2017 and Visual Studio Community 2019 installed.
I am seeing that the recent projects and solutions list is shared between Visual Studio Community 2017 and Visual Studio Community 2019.
For example:
I open Visual Studio Community 2017, open a solution named
A_2017, work on it, close it and finally close Visual Studio Community 2017.
Then I open Visual Studio Community 2019, open a solution named
B_2019, work on it, close it and finally close Visual Studio Community 2019.
Now I open Visual Studio Community 2017 again and check the Recent
Projects and Solutions list and I see B_2019 as the first entry
in there although I never opened that solution with Visual Studio Community 2017.
Is it possible that recent projects and solutions list is not shared among different versions of Visual Studio? If yes please show how.
Thanks
Finally I settled with a work around. For Visual Studio 2019, I installed this extension from the marketplace https://marketplace.visualstudio.com/items?itemName=Danielku15.BetterStartPage2019
And created a group for VS 2019 projects and then added 2019 projects to that group.
This extension also has a version for Visual Studio 2017 as well.
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.
If I download from https://github.com/Windows-XAML/Template10/wiki
and open the template 10 solution in Visual Studio Community 2017 RC, it does not work.
Is it complicated to make it work easily or shall I download vs 2015?
Thanks.
Currently there is no Template 10 extension for Visual Studio 2017, only Visual Studio 2015. As a short-term work around until the Visual Studio 2017 extension is released, you can create your project in Visual Studio 2015 using the Template 10 extension and then open it in Visual Studio 2017 to develop it. There will likely be no Template 10 extension for Visual Studio 2017 until it is RTM. As of this moment, Visual Studio 2017 is Release Candidate version 5 and it is wonderful. I can assure you, since I am the author of Template 10, that Visual Studio 2017 will be fully supported # RTM. https://www.visualstudio.com/vs/visual-studio-2017-rc/
https://marketplace.visualstudio.com/items?itemName=jerry-nixon.Template10TemplatePack
VS2015 should be just fine... VS2017RC will not work....
Is there any reason to keep Visual Studio 2013 installed after installing Visual Studio 2015? If I'm collaborating with someone using VS2013, are there any known problems if I use VS2015?
I don't see any reason to keep VS 2013. VS 2015 opens the same projects without problem.
I worked on the same project from 2 computers, one had VS 2013, other 2015 and didn't have any problem.
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.