silly question: vb6 and xp rutnimes inclueded?

[SteveCRM]

Im want to make an exe, this exe would be much easier to make in VB than C++ (for me). My question is will it work with just a standalone exe....nothing packaged with it? The exe is going to be the autorun of a cd.

thanks guys

[baja_yu]

It depends what the exe uses and does..... and in any case you need to have the msvbvm60.dll installed on the users system (which XP has on install).

[ALL]

I have never had a problem running a VB6 app on a compuer, i know it requires a dll but every computer i have ran the exe's on have had it installed. you shouldnt have a problem

[baja_yu]

It is not good to only relly on the user already having the DLL. Try running your app on a fresh install of Win 95, 98 or ME.

What you could do is download this file:
http://download.microsoft.com/downlo...vbrun60sp5.exe

Include it on your CD along with the main exe (it is 1MB in size).

Have the autorun run a small app made in C++ which will do this:

1. Check for existance of the msvbvm60.dll in the system folder.
2. If it exists run the main exe
If not: run the "vbrun60sp5.exe /q"
(the '/q' switch makes it run silently without user knowing about it or having to do anything)
3. When that install is finished run the main exe

[kleinma]

wow...

first of all there are 6 total runtime files that make up the "VB RUNTIMES"
not just a DLL, and to just assume that any user will have these files is just silly... granted windows 2000 and XP come with them, they DO NOT come with the latest service pack runtimes (maybe new XP builds shipping now do, but not all of them)

second of all they are on service pack 6 with them

[MartinLiss]

I have never had a problem running a VB6 app on a compuer, i know it requires a dll but every computer i have ran the exe's on have had it installed....

You've been lucky.

[numtel]

As long as no custom dlls or controls are used I've found that you can just put msvbvm60.dll (i think that's it) in the same directory as the executable and it will load from there if it can't find it in the system dir

[kleinma]

As long as no custom dlls or controls are used I've found that you can just put msvbvm60.dll (i think that's it) in the same directory as the executable and it will load from there if it can't find it in the system dir

ASYCFILT.DLL
COMCAT.DLL
MSVBVM60.DLL
OLEAUT32.DLL
OLEPRO32.DLL
STDOLE2.TLB

these are the runtimes... and ALL of them need to be registered in COM to work (except for ASYCFILT)... so if what you said worked.. it was because the runtimes were already on the system... POSSIBLY some VERY VERY basic app would run with only the virtual machine runtime DLL... but even then it would still need to be registered on the system.