PDA

Click to See Complete Forum and Search --> : Creating Distributable EXE's


Jbrauman
Aug 7th, 2008, 10:15 PM
Hello everyone,
I have a question for the people who are experienced with Visual basic 6. I want to create a number of different EXE applications, all with different API calls, components referenced etc.. yet I want to make them all standalone EXE's. my question is, what component references/API calls can you do in a Vb application so that it would work on all computers (ones that do not have Vb installed). Or more specifically, what components/API calls shouldn't I put in my applications to avoid a 'component missing' error or such? I want to be able to distrubute standalone EXE's, not have an installer or anything.

Thankyou.

RobDog888
Aug 7th, 2008, 10:58 PM
Thread Moved

You will always need the vb runtimes installed but on XP they will already be present and on 2000 pro and earlier they wont exist and need to be installed.

For a truely "stand alone" app you need to use C++ or such.

Jbrauman
Aug 7th, 2008, 11:00 PM
So basically, a standalone EXE file created with Vb will only work on XP =/

RobDog888
Aug 8th, 2008, 01:43 AM
Just about any language that you may use will have dependancies. Those dependancies need to be deployed to insure that your app will run.

dilettante
Aug 8th, 2008, 08:25 PM
The Visual Basic runtime (msvbvm60.dll) is included in the following Windows operating systems.

Version 6.0.82.44 included with:
Windows NT 4.0 SP4, SP5, SP6, SP6a (Windows 98SE?)

Version 6.0.84.95 included with:
Windows 2000 (Server, Professional, and Datacenter editions), Windows Millenium Edition

Version 6.0.92.37 included with:
Windows XP Home, Windows XP Professional

Version 6.0.96.90 included with:
Windows 2000 SP4, Windows Server 2003

Version 6.0.98.2 included with:
Windows XP SP3, Windows Vista, Windows Server 2008

Hack
Aug 11th, 2008, 11:48 AM
Runtime files are not the only dependencies possible.

Any time you add a control through Project/Controls, either an OCX or another DLL is being reference/used, and that becomes a necessity to include in your installation package.

dilettante
Aug 12th, 2008, 10:32 AM
Very true. About all you can use are the controls intrinsic to VB and possibly controls and classes in system libraries that every OS you want to target has installed already out of the box.