2 ms·
You are overlooking the myriad legacy apps that are entrenched VB6. The owners of these apps would like to graduate to 64-bit and Unicode, to satisfy the custom
by GnarfGnarf 12y ago
You are overlooking the myriad legacy apps that are entrenched VB6. The owners of these apps would like to graduate to 64-bit and Unicode, to satisfy the customers that continue to use the apps and generate revenue. Without rewriting a million lines of code.
- andyjohnson0 12y agoThe best route is to import the vb6 project into VS2008, which will attempt to convert it to vb.net. Then open the project in a later version of Visual Studio. As far as I know VS2008 was the last version to support conversion. I've never actually tried this, having not had the pleasure of being a VB programmer. From what I remember, small projects tended to migrate reasonably well but larger ones could be problematic.
- sssilver 12y agoTheir current problem seems like a fair price to pay for having used a proprietary corporate-backed technology for something as fundamental as the programming language. I hope they'll learn. Looks at C#
- yuhong 12y agoI think the .NET Framework will last a very long time though. Some part of Windows itself depends on it for example.