Alex Clark
8/21/2008 6:58:00 PM
Personally I wouldn't even consider it.
Anything written in VB6 would likely benefit hugely from a rewrite rather
than a code-gen conversion. You'll be able to refactor your code to take
advantage of the enormous language enhancements that have been made over the
years, and VB6 wasn't even truly an OO language, so there'll be plenty of
extra functionality to exploit from the compiler there. I don't think
there's any quick fix for what you want, no matter how good the converters
are today.
"Stephen" <stephenwo@gmail.com> wrote in message
news:c5760f3e-8004-42e2-8627-a97992c2d34a@w1g2000prk.googlegroups.com...
>I have a large VB6 code base that I need to convert to C#. I am
> assuming that the best approach would be to first convert it to VB.NET
> and get it into a compilable state, then to convert it to C# from
> VB.NET.
>
> Problem: I see a lot of converters out there that do a pretty good
> job of performing the conversion. But most of the ones I see do this
> on a file by file basis rather than a project by project basis.
>
> So: what's the best converter out there that will take a VB.NET
> project as input and produce a C# project with converted code as
> output?
>
> Thanks,
>
> Stephen