Based on the early versions released for testing in the last year this doesn't appear to be a problem. If you have been taking the necessary steps to write, compile, and package VB6 programs to run properly under Windows Vista then most of them will run on Windows 7 and on Windows 8 for x86 and x64 with no issues. Win8 on ARM platforms are another story, and VB6 programs will not run there.
But a lot of people have relied on Windows XP application compatibility features even to run their VB6 programs there. They have continued to program as if they are still on Windows 95. This "mostly worked" "most of the time" as long as the WinXP system wasn't properly secured, all users ran as an administrator or power user, etc.
That doesn't quite cut it anymore. While there are still many appcompat features in Vista and later (and actually a few new ones) they can no longer simulate Win9x simply by using admin accounts. If you get lucky a given program might work just fine, others might "mostly work" while still others won't work acceptably.
This isn't entirely a VB6 issue because people have the same issues with VB.Net or C# programs if they have been breaking the rules. Most versions of VS.Net development tools make things a little easier because they support the creation of application manifests for marking programs "Vista aware" while VB6 doesn't have that capability built in. However they still have to observe the rules about where files are stored and what parts of the registry they use.
It is very late in the day to start thinking about the post-XP world no matter what programming languages and compilers you use.
Posting Permissions
Reply With Quote