Solved

How do I migrate an MS Visual Studio 2012 solution to VS 2013?

Posted on 2014-03-10
2
694 Views
Last Modified: 2014-03-10
Hi:

I just downloaded and installed VS 2013.
I've got an existing 2012 based solution (ASP .Net & Web Services).
I was quite surprised to see I was just able to open the project with
no warnings regarding conversion to 2013.

Am I missing something here? Release past, we'd receive notifications that
VS was about to migrate the solution/projects to the latest version.

Is this a case of "it just works," so that the solution/project files
are not altered (no new libraries/external references unless
explicitly changed?)?

I just want to make sure I'm not missing a step/important point.

Thanks,
JohnB
0
Comment
Question by:jxbma
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 29

Accepted Solution

by:
Paul Jackson earned 500 total points
ID: 39918996
Your not missing anything Visual Studio 2012 and 2013 solution files are the same so no upgrade is required for most solution types.

http://msdn.microsoft.com/en-us/library/hh266747.aspx
0
 
LVL 1

Author Closing Comment

by:jxbma
ID: 39919001
Cool Beans. Thx.
I saw references to that but was a little skeptical.

Thanks again.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Wouldn’t it be nice if you could test whether an element is contained in an array by using a Contains method just like the one available on List objects? Wouldn’t it be good if you could write code like this? (CODE) In .NET 3.5, this is possible…
Performance in games development is paramount: every microsecond counts to be able to do everything in less than 33ms (aiming at 16ms). C# foreach statement is one of the worst performance killers, and here I explain why.
This is Part 3 in a 3-part series on Experts Exchange to discuss error handling in VBA code written for Excel. Part 1 of this series discussed basic error handling code using VBA. http://www.experts-exchange.com/videos/1478/Excel-Error-Handlin…

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question