Search

Uncorrected migration from VS2010 to VS2012 by L'Yosha

Active

3
0
Sign in
to vote
Type: Bug
ID: 772032
Opened: 11/23/2012 2:54:55 AM
Access Restriction: Public
0
Workaround(s)
2
User(s) can reproduce this bug
I am migrating a solution from VS 2010 to VS 2012. In "Migration Report", everything was successful, except for one warning:
"Visual Studio needs to make non-functional changes to this project in order to enable the project to open in this version and Visual Studio 2010 SP1 without impacting project behavior."

However, I can't open it in VS 2010. I found that if I change MinimumVisualStudioVersion to 10 in *.csproj, I will be able to open it in VS 2010, but VS 2012 will try to migrate the solution again.

I could change the MinimumVisualStudioVersion value to that in which it will open the solution, but it would seem inappropriate to change the value manually each time I need to open the solution in one or the other version of Visual Studio.

Type of solution is: Visual Studio Package
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

Open solution from VS 2010 in VS 2012, agree with "One-Way upgrade", then try to open it in VS 2012

Product Language

English

Operating System

Windows 7 SP1

Operating System Language

English

Actual results

solution doesn't load correctly

Expected results

solution loads correctly
File Attachments
File Name Submitted By Submitted On File Size  
IncorrectMigrationTestProject.zip 11/26/2012 16 KB
IncorrectMigrationTestProject.zip 11/26/2012 16 KB
Sign in to post a comment.
Posted by M_Olson on 5/3/2013 at 8:41 AM
I have a similar issue, although I have not attempted to open my solution in VS 2010 because it is a SharePoint solution and it would be pointless to do so, now. But I get the message mentioned by L'Yosha EVERY SINGLE TIME I load the solution in VS 2012.
Posted by Microsoft on 12/26/2012 at 9:31 AM
Hello L'Yosha.

VS 2010 solutions that have been migrated to VS 2012 are not supposed to be opened in VS 2010. If you want a Visual Studio Package to still be opened in VS 2010, you need to only use VS 2010 to edit the package.

Thank you
David Zitzelsberger, SDET II, Microsoft.
Posted by Microsoft on 11/27/2012 at 12:32 AM
Thanks for your response. We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by L'Yosha on 11/26/2012 at 5:51 AM
It is simply a VS 2010 "Visual Studio Package" solution that was migrated to VS 2012. As I said, if I change "MinimumVisualStudioVersion" to 10, I can open it in VS2010 and vice versa.

https://skydrive.live.com/redir?resid=6C971D761B68E578!115&authkey=!AL-SFsy2C9RptO0
Posted by Microsoft on 11/25/2012 at 10:49 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a demo project to demonstrate this issue so that we can conduct further research?

Please submit this information to us within 4 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 11/23/2012 at 3:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.