3 ms·
The VB 5 code may run, but Microsoft doesn't support it. And migrating VB 5 to a platform that Microsoft does support can be challenging. Which is why I said,
by btilly 17y ago
The VB 5 code may run, but Microsoft doesn't support it. And migrating VB 5 to a platform that Microsoft does support can be challenging. Which is why I said, "...any language supported by Microsoft today!"
Furthermore the rationale for a lot of that VB 5 code was integration with MS Office software. But that software isn't compatible with current offerings. Therefore if you were integrating that VB into your office workflow, the fact that it still could run doesn't stop you from being under pressure to port.
- gaius 17y agoHow is including a Win16 thunking layer in the OS not supporting it? Try running an app compiled for a 1.x Linux kernel on 2.x... Or even a different libc!
- btilly 17y agoAccording to http://msdn.microsoft.com/en-us/vbrun/ms788707.aspx http://msdn.microsoft.com/en-us/vbrun/ms788707.aspx VB 6 was end of lifed in March of 2008. You can no longer buy support or licenses for VB 6. Microsoft is trying not to break running applications in Windows 7, but has officially said that this will be the last version of the OS with support. On the Linux example, didn't I just say that attention to backwards compatibility is orthogonal to the source being open? I didn't use Linux as my poster child for good reason! And even within Linux, you'll find wide variation between distributions. (Debian being an example that is pretty good, Red Hat being mediocre at best, and Gentoo being infamous for regularly breaking things.)