Having problems opening an SSIS solution file

Question

I have to make some changes to an SSIS package that was last modified in 2009 by a person who has left the company.
I am having problems finding a version of Visual Studio that will open the SLN file. I do not know how the package was originally maintained.
Yesterday, I was able to right-click on the SLN file and select 'version selector', that opened the solution in VS 2005 without me having to select a program. I made some changes and saved, rebuilt and ran the package.
Today when I try to open the SLN the same way, it displays the screen with the various VS version icons on it, but no VS 2005 listed!
The bottom line, is I now cannot open the solution with any version of Visual Studio. If I can find another SLN file that will open, can I copy the modified dtsx file to that solution so all my work is not wasted? It took me 3 days work to modify this package.
Can someone please help, my deadline for this task is TODAY.
Here is the message I get if opening with VS 2005:
Here is the message I get if opening with VS 2010:
Here is the SLN file (It looks like it got modified because I'm pretty sure yesterday it said VS 2005 at the top):
Microsoft Visual Studio Solution File, Format Version 11.00
# Visual Studio 2010
Project("{D183A3D8-5FD8-494B-B014-37F57B35E655}") = "HPAddress_ExportData", "HPAddress_ExportData.dtproj", "{7EB5909F-6836-4B23-A121-9F623FB1C932}"
EndProject
Global
 GlobalSection(SolutionConfigurationPlatforms) = preSolution
  Development|Default = Development|Default
 EndGlobalSection
 GlobalSection(ProjectConfigurationPlatforms) = postSolution
  {7EB5909F-6836-4B23-A121-9F623FB1C932}.Development|Default.ActiveCfg = Development
  {7EB5909F-6836-4B23-A121-9F623FB1C932}.Development|Default.Build.0 = Development
 EndGlobalSection
 GlobalSection(SolutionProperties) = preSolution
  HideSolutionNode = FALSE
 EndGlobalSection
EndGlobal

Answer 1

Hi AllTheGoodNamesWereTaken,
Based on my test, if we open a solution file with lower version in a higher version Visual Studio (VS), it will use Visual Studio Conversion Wizard to update the solution to current version of VS. Then the solution file will also change to current version
of VS. If we open a solution file with higher version in a lower version Visual Studio (VS), it causes an error that “The version number in the package is not valid. The version number cannot be greater than current version number”. And the solution file still
use the original version of VS.
So it seems that the original version of solution file is lower than or equal to VS 2010. Since the VS is backwards compatible, we should use a higher version of VS (VS2010 and later) to open the solution file. Notice that we need open the solution file,
not the project file.
Besides, we can also create a new SSIS project in a higher version of VS, then add the packages with “Add existing package” option from File System. Reference:
https://www.blackbaud.com/files/support/guides/infinitydevguide/Subsystems/bbdw-developer-help/content/tkaddpackagefromexisting.htm
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support