VB6 runtime files?

[datwig]

Many sites offer programs created in VB6. They also have VB6 runtime files availible for download.

I want to know if those files are NEEDED by every program that I create in VB6. Are they? Or are they only needed when I add a modual or something to my project?

[Tek]

Yes they are needed. Vb6 is not a full complile language like C++ is. Vb6 is a interpreted language. Even if you compile into native code it is still interpreted and there is no linker ect..... Now you say what interprets the code. Well the Vb6 runtimes. They are absolutley required even if you want to run a simple Hello World app.

One day I am sure VB will be a full linked language but for now we must settle with the runtimes.

[datwig]

Does windows XP or any other operating system come with these files?

[TheVader]

No, there are no OS's that come with the runtimes. You really have to include those files when you distribute...

[Tek]

Currently the only Runtimes distrbuted on a OS is the .Net Framework. That is distributed on the newest versions of XP. Forexample you just bought it in a store within about the last month or 2.

As for the VB6 runtimes. they don't come with the os. You can either distribute then with your program or you can put them up for download on your website with a Warning Msg that they will need to download them if they never did.

[plenderj]

All modern OSes come with the latest VB6 runtime files.
And Visual Basic is not an interpreted language - it is a fully compiled language, but part of that compiled code makes function calls to particular dynamic link libraries - thus the reason for needing the vb runtime files.

[VBGuy]

Actually, XP (and Win 2000) shipped with the VB6 runtimes. Currently no OS is shipping with the .NET framework.

We just just broght 30 new XP boxes online and loaded them with our volume lic. copy of XP Pro SP1a. All have the VB runtimes but do not have the .NET framework (had to have our intern install it).

[plenderj]

Actually though I do think that Windows Server 2003 is shipping with the .Net framework installed. Albeit the older version of it I think but I'm nearly certain it does come with it installed ...

[randem]

datwig

The VB runtime files you refer to are the universal runtime file for VB that will run on any windows OS. If you find the runtime files on your OS they may be specific for that version of the OS and contain newer or updated function that may not work on older OS's.

This is why, If you distrubute your app. You should ALWAYS use the universal versions on these runtime files. Or whom ever install the app on a system that is unlike yours may have problems runing your app and you may not readily know why it does not work.

It's the "I DON'T KNOW WHY IT DOESN'T WORK FOR YOU, IT WORKS HERE" Syndrome.

[datwig]

OK, everyone is saying different things about whether or not certain OSs some with the VB6 runtime files.

Where would these files normally be. I remember having to download them before I started VB programming. The website said either put them in the folder that the program is in or in a system folder which I don't remember. What is the system folder? Would the runtime files most likely be in there for me?

Where would I check on a freshly installed XP for the runtime files?

[randem]

datwig

On a freshly installed OS... You may not have them all (No OS version comes with the VB runtime version needed). You only get them after installing VB or some other program that uses them in their install (maybe different on latest OS).

Now the problem is on which version of the VB runtime files were installed with the app. There is only one version of VB runtime files that are guaranteed to work on every OS.

The others are missing some functions or some of the functions were changed. So in either case you need the version of these files that has everything your program needs in the way it is expected.

This is why MS released the vbrun60sp5.exe file. It can be installed and should replace your old files. I personally do not believe you should use this approach unless you double check that the files are actually replaced (expecially on Me, 2000 and XP). the problem with this approach is everytime you install a program it may change your VB runtime files again.

Those systems have functions that will not allow older versions of dll's to be re-intorduced to the system and they will never take. The ones that never existed will be copied but the ones that already existed will not be replaced. This was to remedy what was known as DLL hell.

This was where you had mis-matched dll's on your system and it was almost impossible to fix. I myself place these files into a separate directory so that I know where they are and all installations that are created use that directory to pull the VB runtime files from, so not to create ANY problems or mistakes.

I suggest you do the same!!!

You can get the files from here: http://www.***********/support/support.htm