Should I migrate directly from VB 6.0 to C#, or is it reasonable to use a 2-step strategy (VB6 –> VB.NET –> C#)?
We’ve heard a few people suggesting a double path approach for those who chose to migrate their VB6 applications to C#. This suggestion mostly comes from those who offer a solution that only converts to VB.NET, and they even say it’s irrational to even think about jumping from VB6 to any .NET language other than VB.NET. Well, about half of our customers know better. The differences between Visual Basic 6.0 and any .NET framework compliant language is totally noticeable, since, for starters, the former is a procedure intensive, non structured programming language which strongest feature was the “visual” designer used to build the graphical user interface, while the latter ones are fully Object Oriented. This immense set of differences between VB6 and C# or VB.NET are estimated and resolved in most scenarios by ArtinSoft’s Visual Basic Upgrade Companion tool. To be more specific, let’s use some particular VB6 inherent feature, which is also present in VB.NET by the way: the “OnError Goto
Related Questions
- Would elective cesarean section for suspected macrosomia be a reasonable strategy for decreasing the number of shoulder dystocias and brachial plexus injuries?
- Should I migrate directly from VB 6.0 to C#, or is it reasonable to use a 2-step strategy (VB6 –> VB.NET –> C#)?
- Does VB & C# to Java Converter convert VB6 projects to Java?
