If you're reading this, you know the story: Hundreds of millions of lines of
perfectly good (well, mostly good) VB6 power an incredible array of business applications.
And now, Microsoft doesn't support VB6! .Net has taken over, like it or not!
Conversion to a supported technology is not optional. If your business is to run as well tomorrow as it did yesterday, that Visual Basic must be converted!
When you get your VB6 converted, you need someone who:
And now, Microsoft doesn't support VB6! .Net has taken over, like it or not!
Conversion to a supported technology is not optional. If your business is to run as well tomorrow as it did yesterday, that Visual Basic must be converted!
When you get your VB6 converted, you need someone who:
- Has written and maintained VB6 code. The best VB.Net or C# programmer will be at a disadvantage without VB6 experience.
- Is willing to do more than merely run the conversion tool packaged with VB.Net.
- Knows what really needs to be upgraded manually (think data access) and what probably doesn't (think form layout)
- Understands that sometimes a full re-architecture plan is neither necessary nor cost effective
- Understands that other times that full re-architecture plan is appropriate. A lot has to do with the amount of future development that is anticipated
