Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

convert vb6 project to .net using VS2010 Express?

I can't seem to convert my vb6 ActiveX dll project (.vbp) to .net using VS2010 Express.

Is there another way?

UPDATE

So now that Microsoft has stopped offering a VB6 migration tool (VS2010). Should I migrate to .NET 3.5 instead and use VS2008?

Get it to .Net and then migrate it up to 4.0 when ready...

Thoughts?

like image 400
webdad3 Avatar asked Apr 19 '11 02:04

webdad3


People also ask

Can you convert VB.NET to C#?

Code Converter (VB - C#)Adds context menu items to convert projects/files between VB.NET and C#. Flexible: Convert a small selection, or a whole solution in one go, in either direction. Accurate: Full project context (through Roslyn) is used to get the most accurate conversion.

Is VB.NET compatible with VB6?

Applications written in both VB6 and VB.NET can also be installed and executed on the same computer. Furthermore, components written in VB6 can be used in VB.NET projects. Fortunately, there is a tool to assist in some of the modifications you must make to your programs and projects.

Does .NET support VB?

Microsoft announced that with . NET 5, VB's supported project types will increase beyond Class Library and Console applications to also support: Windows Forms.

Is VB6 and VB.NET same?

VB6 was interpreter based language while VB.NET is a compiled language. VB6 is non-object oriented principle based language. Whereas, VB.NET , from a coding style perspective looks similar to old VB6, but, has more power to it, just because it sits on the . Net platform.


1 Answers

In answer to the updated question: I recommend reading Microsoft's advice page. It gives a good overview of your five basic options (migrate, extend, rewrite, replace, do nothing). You need to think about the pros and cons of each option and how important they are to you. There is no one-size-fits-all answer to this question.

Migrating to .Net using Visual Studio 2008 targets .Net 3.5 and gives you a dependency on Microsoft.VisualBasic.Compatibility.dll (the VisualBasic.Compatibility namespace). That has been marked obsolete in .Net 4, so it may be dropped in a future version of .Net. That is an argument in favour of the commercial migration tools, or rewriting.

like image 85
MarkJ Avatar answered Nov 12 '22 19:11

MarkJ