Plan for VB3 to VB.NET/IL Converter

After a couple of meetings with clients still employing VB3 programms, I come to the conclusion, there is need for a "VB3 to .NET" migration tool. There´s still a lot (!) VB3 software running out there - and developers see no way to move it anywhere. Jumping onto the VB6 bandwaggon is not really the thing to do anymore - and an alternative is not in sight.

Microsoft hasn´t been able to provide a 100% migration path for VB6 to VB.NET due to several reasons - one of them being VB6' object orientation.

With VB3 I don´t see that many hurdles in the way of a real (!) migration tool. It could either be a VB3 to VB.NET/C# converter. This then would be a one way street resulting in a new codebase to be maintained with VS.NET.

Or, I guess, translating VB3 directly to IL or even translating P-Code to IL would be possible. That way, the sources could still be maintained using the old tools.

I don´t know yet, which way to go. But I´ll start soon after some tests. (VBX integration is still kinda mindboggling :-)

4 Comments

  • Go Twin go! The old VB god comes back ...

  • Why would you change the runtime environment, without changing the development tools?



    I would think the whole reason for migrating working code to the .NET platform would be to ease future development.



    I don't see the benefit of creating a PCode -> IL translator (except that it might be an educational experience).



    So, I would vote for creating the code base migration tool.

  • YES NO

    a VB convertet to .net would not make sense. The thinking of the developer have changed. We both know how VB 3 programms were developed!



    The other point an IL converter is a quite good idea.

    I would extend it and say: we need a Vb 7 which can create IL and Win32 Code



  • build it and we'll buy it

Comments have been disabled for this content.