VB6 to VB .Net

  • Thread starter Thread starter Matt
  • Start date Start date
M

Matt

Hey,

I would like to know if it's easy to update an application (big) from
VB6 to VB .Net?
Is it easier to re write the application?

Is there a problem if I still keep the code in VB and add some module
in VB .Net? Compatibility, support for VB 6 by Microsoft... I would
like this application to run for at least 5 more years

Thanks for any advice
 
First, please post to microsoft.public.dotnet.languages.vb. This is a C#
group. Now for the short answer - it depends on what your application is
doing. Frequently it's easier to rewrite than port.

Mike Ober.
 
Hey,

I would like to know if it's easy to update an application (big) from
VB6 to VB .Net?
Is it easier to re write the application?

Is there a problem if I still keep the code in VB and add some module
in VB .Net? Compatibility, support for VB 6 by Microsoft... I would
like this application to run for at least 5 more years

Thanks for any advice

You'll get more hits if you post to microsoft.public.dotnet.languages.vb.

As for your question, there is a wizard that migrates the project to .NET,
as well as an advisor application that tells you how best to prepare for
the migration.

Beware though the wizard is only 70 or so % efficient. Some code will
definitely have to be rewritten
 
Matt said:
I would like to know if it's easy to update an application (big) from
VB6 to VB .Net?
Is it easier to re write the application?

Is there a problem if I still keep the code in VB and add some module
in VB .Net? Compatibility, support for VB 6 by Microsoft... I would
like this application to run for at least 5 more years

As other have stated then there are better groups than this.

One advice though: there are two aspects of this.

1) Will it be easy to get the VB6 converted to VB.NET
that function equivalent to the VB6 ?

I am skeptical but you can give the tools a chance.

2) Will it be easy to get the VB6 converted to VB.NET
that is nive .NET code that will be easy to maintain and
extend in the future ?

I am extremely skeptical about that. I think you will need
to rewrite to really benefit from .NET !

Arne
 
Back
Top