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.
Related
I recently got a Win 11 machine and installed Visual Studio 2022, then I installed Visual Studio 2019 to support an old app. In the search feature on the Win task bar, when I enter visual studio it shows them listed like this:
Visual Studio 2022
Visual Studio 2019 (2)
It has this for "Blend" too.
Is this just from picking the same feature set(s) during the install? For example, SQL Data Tools. And/Or could it mean something isn't right with my env?
VS 2019 is in
Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\devenv.exe
VS 2022 is in Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\denvenv.exe
I'm having an issue with an old site in 2019, but I don't believe it's related. I am just curious why that (2) is there and what if any problems it could cause.
Thanks
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.
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.
Hi guys im using Microsoft Visual Studio 2013, but in my college, all of the computers using microsoft visual Studio 2012. Is there is possible if i save my project (from visual studio 2013) then i open it on visual studio 2012?
Visual Studio 2013 has a feature called "Solution Round Tripping", which means that a solution created in Visual Studio 2012, under certain circumstances, can be edited by both Visual Studio 2012 and 2013.
There are limitations though, as you can't open a solution in 2012 that uses new features or frameworks that are not available in 2012. Makes sense right? Generally, when you create the solution in 2012 and then open it in 2013, your chances are high.