Upgrading Visual Studio Project from 2010 to 2017 - visual-studio-2010

I have an older project that was written in VS 2010 a few years back, and now I need to make some changes to it. I'm personally working in VS 2017, and for some reason, every item in the designer needs to be resized and realigned. Is this common? Because my coworker opened it in VS 2013 and it looked fine.

Related

Visual studio upgrade

I have a Visual studio web forms project that is written in vb.net 4.8. It was originally built in VS 2012. At some point, I got a free version of VS 2019 to try and opened the project. After a few weeks, I scrapped VS 2019. Now when I open the project in VS 2012, it churns for a moment and VS crashes.
VS must have upgraded my project to work with 2019 and added some pieces that don't work in VS 2012.
How do I downgrade the project so it opens in VS 2012? or can I rebuild the project so it works in VS 2012?
I tried downloading VS 2019 and opening the project. The project kept crashing VS. I created a new project in VS 2019 and imported the files in. After adding them to the project, I had about 5 warning preventing the program from building. Once those were addressed, I could run the project. I will now have to upgrade to the latest version of VS.

Visual Studio 2019 or 2022 IDE don't save new bookmarks of project created in earlier IDEs

I developed a project in visual studio 2012 year ago but migrated to visual studio 2019. However, the bookmarks and the files opened won't save in the newer IDE. I have tried database and environment data clean up, cleaned solution and built, but it won't work. I have asked at least two times on Microsoft forum, now migrated elsewhere, to no avail. Any help?

Should I install Visual Studio 2017 beside Visual Studio 2015 or should I first uninstall Visual Studio 2015 and then install Visual Studio 2017?

I am currently using Visual Studio 2015 for programming ASP.NET Core applications. I have the following questions regarding installing Visual Studio 2017:
What is considered to be best practice and/or cleanest method?
Should I install Visual Studio 2017 beside Visual Studio 2015?
Should I first uninstall Visual Studio 2015 and all .NET Core dependencies and then install Visual Studio 2017?
Are there any tools that would ensure a clean uninstall of Visual Studio 2015?
From page Visual Studio 2017 Platform Targeting and Compatibility
Compatibility with Previous Releases Installation
You can install and use Visual Studio 2017 alongside previous versions of Visual Studio, including Visual Studio 2015, Visual Studio 2013, and Visua Studio 2012.
So yes. you can install them without any problem.
VS 2013, VS 2015, and VS 2017 all work well side-by-side. VS 2012 can be a little dodgy on Windows 10, but should also work side-by-side. In theory VS 2010 should also work side-by-side with those, but I've run into quirks in the past with them interfering with one-another.
Projects should round-trip between 2015 and 2017 generally, although there are some one-way upgrade scenarios.
Note that if you really just need the older compiler toolset for some reason, you can also install VS 2017 and select the optional component Microsoft.VisualStudio.Component.VC.140 which installs the older v140 compiler which you can still use with the VS 2017 IDE. That said, there's not a lot of reason to do this since the VS 2015 & VS 2017 C++ standard libraries are binary compatible so you can mix them in a project.
See this blog post for information on VS 2017.
It sounds like you have done some projects in 2015 already, so you will probably want to keep it.
Once you open a project in a new version, it will try to upgrade the project and then you can't go back.
However, if you have multiple versions installed at the same time, when you try to open a project, say, from Windows Explorer, it will open it with the "Visual Studio Version Checker" and will look at the project file and determine which version to open it in.
Bottom line, if you have the hard drive space, there is no reason to not install them alongside each other.
In the past, it was recommended to install them in sequential order if you are installing multiple versions, but it doesn't sound like this is an issue for you and I don't know if that is even a problem anymore as it has been several versions since I have had to deal with that.
Good luck!
Personally, I would keep both - there have been multiple times through the years where you have compatibility issues and NEED to have the prior version(s). I've also had old project that will not upgrade and I've gone back and reinstalled old VS versions.
If you have no reason to keep VS2015 in your computer I would suggest uninstalling it.
I uninstalled VS2015 after installing VS2017 and later noticing that I was still using an old taskbar shortcut to VS2015.
So I was inadvertently still using VS2015.
Maybe some special cases require keeping older versions of VS along side the new version, but for the rest of us, I say, uninstall!
VS 2015 is the last version that is supported by Installshield LE.
If you have a need for building installers in the future, it will be useful to have VS 2015
1,2,3. Visual Studio 2017 has more features over 2015 and it contains 2015's current features so you don't need 2015 alongside 2017. Just stick with 2017. And I don't think you will have any problems while opening 2013 and 2015 projects with Visual Studio 2017.
Uninstall Tool is a good tool to use. It cleanses all the leftover files and registry entries after running the original uninstallation wizard and even tells you how many files will be cleaned after the required reboot.
For people continuing to read this, I have Visual Studio Professional 2008 (For Windows Embedded 6.5), 2010, 2015, 2017 and they all work even if open at the same time.
Edit: As stated in other answers, they need to be installed from oldest version to newest.

Disable visual studio 2013 old project converter

Recently, I installed VS 2013 for my own computer. However, I still have some project that created by VS 2010. The uncomfortable thing is, my VS 2013 automatically convert my old project to VS 2013.
Is there anyway to disable the automation conversion of VS 2013?
EDIT: Instead of opening the project by VS2013, it should work well with Visual Studio Versions Selector. However, the issue can appear again on project that was used to be developed on VS2003, VS2005 and VS2008

Visual Studio 2012 Website Does Work Properly in Visual Studio 2012

I originally created an ASP.NET site in Visual Studio 2010 a few years ago and it went through the VS 2010 SP1 update as well. This meant that Visual Studio 2012 opened the solution without performing a one time upgrade.
The issue I am having is that the built-in browser selector in Visual Studio 2012 is not available for this project and the settings only let you use the default browser.
When I looked in the .SLN file, the version line indicates Visual Studio 2012 (i.e. # Visual Studio 2012) and no other setting in there appears to have anything to do with this limitation.
Has anybody had this issue and, if so, can you please let me know how your overcame it?
Thanks!
You're going to have to upgrade your project to allow it to make use of Visual Studio 2012 only features. Note, if you do this you will no longer be able to open your project in earlier versions of VS.
http://msdn.microsoft.com/en-us/library/hh266747%28VS.110%29.aspx
For VS 2010 , you can install WoVS Default Browser Switcher extension
Also a related question Change default browser in Visual Studio 2010 RC

Resources