By Imran Salahuddin | June 2nd, 2015 |
Migrating VB6 to .NET is not just about loading it to the new version. Some may already know but, VB6 does have its own built-in migration device, it actually is really good at altering syntax. As a professional, I have to be honest, that’s just half of the job. Your assignment won’t assemble right away and not to mention, you’ll have a lot of concerns in the future.
Even corporations that are pleased with their VB6 face the burden to move on. If you aren’t equipped, you might elect to not migrate at all.
The problem with this theory is that there are a few of those corporations that cannot continue using this unsubstantiated platform. Especially from a security or banking perspective, those types of regulations wouldn’t allow it anyway.
There are plenty of technical encounters when it comes to recycling code and moving it from VB6 to the .NET setting. To some extent it gets easier to migrate from VB6 to .NET because .NET incorporates some of the old configurations. Always keep in mind that if you really want to the full benefit of the .NET, then the issues you will face get worse.
No matter how you look at it, there is a huge price to pay for compatibility. Let’s contemplate for a second about what this really means to your business. Let’s just say, you used VB6 to build applications that play a very important role in your corporation. And in those apps there are hundreds upon thousands of lines of VB6 code. The databank design is based on ADO, the former COM-based database model.
At this time VB6 is at the end of the line. What do you do?
It’s a bad I know but it happens more times than not. Even Microsoft recommends you either migrate to .NET, or hold/freeze the current app to maintenance only mode, then create different features in .NET via interop methods to incorporate the old with the new.
See, I told you that it could get worse in a hurry. Migrating takes a huge effort from all parties involved, performance problems as well as sneaky programming glitches is another.
Applications that use good tactics in relations to sorting out business logic and presentation code, which in essence, uses an object-oriented scheme, and is much simpler to migrate than those that don’t.
Are you handling VB6 applications presently? And if so, what is your strategies moving forward?