On what versions of windows are vb runtimes included?(and other deployment questions)

[VaxoP]

Hiya
What versions of windows come with the vb6 runtimes?
Also, if you program in vb6 sp5 and you deploy that program on a computer that only has the vb6 runtimes (no service pack) - will that program work on that computer?

[RhinoBull]

No one should ever rely on what maybe installed on the destination machine - always (and I mean always!) supply your clients with full distribution package.
In my opinion that is the only guarantee that your app is going to work.

[VaxoP]

Yes I have hired a c++ programmer to code me a program to check if the runtimes are present and if not download and install them, but I was curious as to which versions of windows actually come with the runtimes.

And.. if my program is coded in sp5 will it work on a computer with no sp?

[RhinoBull]

As far as I know VB6 runtimes are included in XP and Vista. I think theye were included in Win2K as well but not quite sure about it.

[MartinLiss]

Moved.

[si_the_geek]

And.. if my program is coded in sp5 will it work on a computer with no sp?

It might, but it depends what your program does. Not surprisingly, the Service Packs fix bugs and/or add features.. so if you use an older one it will include those bugs (or not have the features), and your program may fail. A later SP may not have bugs that you actually rely on!

To know whether it will affect your program, you will need to fully test your application against that particular SP (even if you have tested against earlier/later SP's). This means fully testing your application against all 8 sets of runtimes (no sp, sp1-6, and sp6b).

The same goes for any additional components/references that you use, so you need to test each version of those components against each version of each other, and each set of runtimes. If you have just two components/references, and they have only two versions each (which is extremely low!), that means you need to fully test your application: 2 (component1) * 2 (component2) * 8 (runtimes) = 32 times!


If you aren't willing to test your application (fully) all of those extra times then you will just have to hope it works..

..or simply ensure that the version(s) you have tested against already are installed, by providing a full installation package.

[randem]

You should never count on someone checking for the runtime file. Other apps often install mis-matched versions or partial version which can throw your checking off. The absolute safest way is to include them. A decent installer will check the file versions before installing them and will only install the later versions. Adding checking and download just further complicated the issue especially if the user has no internet connection.

Don't over-complicate the installation... or even complicate it...

[dilettante]

To know whether it will affect your program, you will need to fully test your application against that particular SP (even if you have tested against earlier/later SP's). This means fully testing your application against all 8 sets of runtimes (no sp, sp1-6, and sp6b).

Worse than that, there was a 6a and also the version shipped in Vista, which is later than 6b.

It is safest to develop and deploy with the latest available service pack. The Vista changes were most likely Vista-specific so don't worry about them. Vista won't let you install over its copies anyway.

In some rare cases it may be necessary to deploy relying on whatever runtimes are installed. This is where the testing comes in, and it will never be perfect. For those reasons it usually isn't practical because of the cost (effort) and possible failures down the road.

To some extent you can use soft virtualization techniques to deploy the runtimes with your application without installing the runtimes globally. Some of this can be done through DLL Redirection and some more through SxS manifests. This is somewhat exotic yet and tools and documentation are scarce, plus it requires Win2K or later (XP or later for manifests).

"Harder" virtualization (such as Thinstall) is another option but this is even more exotic, and requires tools that aren't cheap:

Pricing in North America starts at $4,995 for Thinstall Virtualization Suite and a distribution fee applies.

The virtualization market is heating up and "big boys" are pushing up prices as they find ways to make it look more valuable to Corporate users. VMWare is buying Thinstall out:

VMware to Acquire Thinstall