VB6 Runtime file version

[RCox]

Has anyone found a definitive statement by MS or others about which VB6 runtime files are compatible with which Windows versions? For example, the VBRun60sp6 versions dated December 2004 show that they "Apply" to Microsoft Visual Basic 6.0 Learning/Professional/Enterprise additions. This set contains version 6.0.97.82 of Msvbvm60.dll. Since it is an update to Visual Basic 6, I would assume that this set of files is compatible with any version of Windows that VB6 runs on.

Then there is the "cumulative update rollup for the Microsoft Visual Basic 6.0 Service Pack 6 (SP6) Runtime Extended Files" dated May 2009. This is a re-release of the VBRun60sp6 files, but does not include Msvbvm60.dll according to the listing. This update "applies to" XP, Vista, Server 2003, and Server 2008. I assume that the main run-time file is not included because it is part of the respective OS in this case.

So, do I have to distrubute two sets of VB runtime support files, one which includes Msvbvm60 version 6.0.97.82 and it's associated set of files (Comdlg32.ocx, etc.) for Windows 95/98, Me, 2000, and (possibly) XP and then another set to include those files (in the cumulative update rollup) which support the included Msvbvm60 in Vista and eventually Windows 7? Or do the cumulative rollup files supposedly support earlier versions of Windows and the Msvbvm60 that works with them but aren't tested because those earlier Windows versions are no longer supported by MS?

I've spent hours searching for this information but can find no definitive answer to the questions posed. Any help would be appreciated.

[Keithuk]

Welcome to VBForums RCox.

Well the RunTime files are a bit strange. I use VB6 with SP6 installed I don't know if you do. So I make apps and take them to work on WinXP machines with the standard msvbvm60.dll installed and all my apps work perfectly.

If you making an installation package for your apps then as it installs it should check if your trying to install a newer version on a specific file before in puts it in the Win\Sys folder. If it is newer then it gets installed.

Now msvbvm60.dll is installed by default on WinME/Win2k/XP/Vista and a assume 2003.

Now I wouldn't bother using P & D Wizard as its 11 years old now I would recommend you use Inno Setup, its free. Do a search for these words on here. ;)

[RCox]

I do use Inno Setup and have for several years. Even with IS however, I like to take a stab at what "should" be done as far as file installation by restricting what gets installed into what Windows version.

[si_the_geek]

Thread moved to Application Deployment forum (which is where questions about installing/distributing your software belong)

I haven't dealt with including the cumulative update rollup before, but I suspect that your assumption of it being untested/unsupported by Microsoft for earlier versions of Windows is correct.

What I would do is install both sets, but get the installer to make backups of any files that are overwritten (so if things do go wrong, you can fix it).

The FAQ thread at the top of this forum includes a link to Inno Setup instructions for packaging VB6 programs, which is likely to include some kind of useful info.

[RCox]

I have checked out the IS pages on VB runtime support files, but they don't address the situation of the collection of cumulative roll-up files. A post on their forum merely resulted in a reply of "try it and see if it works." I like to be a little more considerate than that. Even if I thoroughly test my program (on Win95 for example) with the cumulative roll-up files and it has no problems, I am hesitant to change these files on a user's system if it may make some other vb6 program (which may use routines that mine doesn't)crash.

[Nightwalker83]

From the Microsoft website:


Source: http://www.microsoft.com/Downloads/details.aspx?familyid=9EF9BF70-DFE1-42A1-A4C8-39718C7E381D&displaylang=en

System Requirements

* Supported Operating Systems: Windows 2000; Windows 2000 Advanced Server; Windows 2000 Server; Windows 2000 Service Pack 2; Windows 2000 Service Pack 3; Windows 2000 Service Pack 4; Windows 95; Windows 98; Windows 98 Second Edition; Windows ME; Windows NT; Windows Server 2003; Windows XP


* Microsoft Data Access Components (MDAC) 2.5 or later
This is the same version MDAC that is installed by the Microsoft Windows 2000 operating system and can be found here.

* Internet Explorer 5 or later is recommended for Service Pack 6. The latest version of Microsoft Internet Explorer, is available here.


As Keithuk said since Vista came after the release of SP6 I would think it would be included as part of Vista from the get go.

[si_the_geek]

That does not include the "cumulative update rollup..." which is much more recent than the runtimes (and does not contain all the files from them).

The issue is how to get both sets to play nicely, on any version of Windows.
I have checked out the IS pages on VB runtime support files, but they don't address the situation of the collection of cumulative roll-up files. A post on their forum merely resulted in a reply of "try it and see if it works."That isn't too helpful, but is likely to be the best you get unfortunately - there is a general lack of knowledge when it comes to VB6 installations these days, as many of the people who used to deal with it properly have moved on to .Net by now, and the circumstances have changed a fair bit in the last few years.

There is some info about the cumulative roll-up here which may help: http://www.vbforums.com/showthread.php?t=550276
I like to be a little more considerate than that. ...I know what you mean, hence my suggestion of creating backups of the files... but based on the thread I linked to it seems that it is not a good idea either - because you cannot uninstall the rollup package (not too surprising, as it includes fixes to security issues).

I have no idea whether something like a side-by-side installation would be apt (info on that kind of thing here), as that may have a similar effect.

It would certainly be my preference to include the rollup, but due to the complexity of testing etc (with other peoples apps too!), avoiding it would be understandable. If you install just the runtimes (and do it properly), at least it wont overwrite the rollup if it has already been installed... and perhaps Windows update will automatically 'upgrade' to the rollup.