migrate from vb6 to vs 2013

Question

0.00/5 (No votes)

See more:

Hi
I want to migrate from vb6 to vs 2013, this is my first project to migrate. I searched in google most of all every body as given as we can migrate from vs 2008. whether any chance directly migrate from vs 2013. if you have any suggestions please.

Regards
Sheethal

Posted 27-Jul-15 2:19am

smsheethal

Updated 30-Oct-20 20:33pm

Add a Solution

2 solutions

Solution 2

Hi Sheethal,

As you know VB6 is one of the good old technology, But i just want to know how many KLOC you are planning to convert.

You can refer below links for your refernce,

https://msdn.microsoft.com/en-us/vstudio/ff793478[^]

https://msdn.microsoft.com/en-us/vstudio/dn569303[^]

http://www.vbmigration.com/[^]

Best Regards,
Vijay

Posted 27-Jul-15 2:36am

VijayPd

Comments

smsheethal 29-Jul-15 3:52am

Hi Vijay

As per given link I tried to migrate but lines of cods are more. so I tried from Visual studio 2008. in wizard I am getting error as
"Unexpected exception occurred during upgrade engine operation: Not able to bind to the source (Exception from HRESULT: 0x8004000A (OLE_E_CANT_BINDTOSOURCE))"
How to

Resolve this issue

CHill60 29-Jul-15 9:44am

The way to resolve your issue is to follow the advice in Solution 3 - do not "migrate" the code, especially using wizards. Rewrite in .net using the original as a reference.
It will be quicker, more robust and more maintainable.

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Accepted Answer · 2015-07-27T02:56:00

Honestly, your best bet to to just scrap the VB6 code and rewrite.

Sure, there are some tools to upgrade the code for you, but it's code written in VB.NET to mimic what VB6 did for backwards compatibility. It is NOT code that should be used to teach yourself VB.NET.

The last version of Visual Studio to have the VB6 upgrade Wizard was 2008. After that, you're either using some third party tool or you're rewriting by hand. Rewriting is really the best option.