Going from VS 2005 to VS 2013 (Visual Basic.net) - What (if any) are the issues?

I am currently using Visual Studio Pro 2005 and programming in Visual Basic.net.  I am thinking about getting VS Pro 2013.

Can I open my current 2005 programs in 2013, edit them, save them, compile and deploy them with 2013?

What issues might I encounter?  I'm wondering how much of a learning curve there will be and major differences.

Thanks
sqdperuAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Éric MoreauSenior .Net ConsultantCommented:
Is it a winforms App? In This case, there should be any problems. Be sure to change the targeted framework to at least 4.0
0
trinitrotolueneDirector - Software EngineeringCommented:
There are many differences moving from VB 2005 to the current version. One of the things being that migrating a 2005 project to a higher version using the conversion wizard will usually target .Net 2.0 by default. You might need to manually change the .Net version being targeted.
Just this one change will break a lot of the old code

I would suggest that you try converting the old project to 2013 and see what conversion errors arise

Here's an article which might help. It targets 2008 but most of it should apply to 2013 as well
http://msdn.microsoft.com/en-us/library/ywsayxak(v=vs.90).aspx

Also have a look at this converter
http://vsprojectconverter.codeplex.com/
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
AndyAinscowFreelance programmer / ConsultantCommented:
You should not experience any particular problems.
Just remember the conversion is a one way process.  The VS 2013 solution can not be opened in VS 2005 at a later date.
As to new things - there will be quite a number to learn especially the extensions/new classes brought in by later versions of .net.  (Rhetorical question: But for your current app if it works do you need them?)
0
David Johnson, CD, MVPOwnerCommented:
If you change the targeted framework  you may find some depreciated items or items that have been replaced by newer constructs.
0
sqdperuAuthor Commented:
Thanks everyone for the advice!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.