First of all, this issue has nothing to do with the installation of SSDT. I have the lastest version installed, at the time of writting this.
My issue is that the SSIS package was written some time ago using, I think either VS2005 or VS2008 as I was using Windows 7 with the lastest SSDT package fro the time, and I now need to open it up to view the workings.
I am now using VS2019 on Windows 10, again with the latest SSDT package, and studio refuses to open the project.
Unsupported
This version of Visual Studio is unable to open the following projects. The project types may not be installed or this version of Visual Studio may not support them.
For more information on enabling these project types or otherwise migrating your assets, please see the details in the "Migration Report" displayed after clicking OK.
- Contessa.SQL.SSIS, "G:\Work Stuff\Solution\40 SQL SSIS\TestSolution.SQL.SSIS\TestSolution.SQL.SSIS\TestSolution.SQL.SSIS.dtproj"
Non-functional changes required
Visual Studio will automatically make non-functional changes to the following projects in order to enable them to open in Visual Studio 2015, Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1. Project behavior will not be impacted.
- Contessa, "G:\Work Stuff\Solution\TestSolution.sln"
I have found the answer and it had nothing to do with the SSDT installed.
After finding this article.
visual-studio-2019-open-solution-file-incompatible
It explains the need to make sure that the SSIS Extension is enables. In my case it needed to be installed.
This occurred because I had installed various versions of SSDT which caused Visual Studio to need me to reinstall.
I recently updated to Visual Studio 2022 Preview 2.1 but it constantly hangs when editing razor files.
I would use Visual Studio 2019 but it is not so simple as I have made extensive use of the global using directive.
I was wondering if there was a way to downgrade to the earlier preview of Visual Studio 2022 Preview 1.1 which worked very well.
I found a site where one could find all previous releases of VS2019 however that is not of much use to me.
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.
Short story - my Roslyn .vsix analyzer does not do anything in VS 2013.
I have a VS extension (.vsix) built with Roslyn, quite close to the ones described here tutorial for analyzers and tutorial for fixes .
I used VS 2015 Community to develop the extension. It works ok in debug instance of VS 2015 and, when I install the resulting .vsix, in normal VS 2015.
I have configured the manifest to also allow installation into VS 2012 and 2013 and installed it into VS 2013 Community on the same machine, however, it doesn't work. It shows up in the list of installed extensions (and the studio was launched after it was installed), but does not show diagnostics and code fix suggestions.
Am I doing something wrong, or are Roslyn .vsix extensions only for VS 2015 and later?
Roslyn was only introduced to VS in VS2015, so no, Roslyn based VSIXes will not work in VS2013.
I've used TestDriven.NET in the past (with Visual Studio 2005), but now that I've got a new installation of Visual Studio 2010 on a different computer, I can't see either the Add-In Manager, or the TestDriven.NET stuff, even though I have them installed.
Help, please! It's making me bonkers.
Note: trying with current version (3.0)
This problem was due to the fact that I was using one of the free versions of Visual Studio, which did not allow for Add-ins.