[RESOLVED] Diffrence between .exe / complete setup file

[make me rain]

In VB6.
What are the differences in distributing a application between
distributing only a .exe file / distributing a complete set up file.

[si_the_geek]

Just an .exe file might not work, and even if it does it may not work correctly and consistently (eg: you may get intermittent bugs if there is an old version of the runtimes installed).

A complete set up package will ensure it works.

[make me rain]

thank u for replay
that means if i reference some library's during design time or if i use some activex controls / addins all is going in to target machine
for eg:- using library reference instead of late bindings, using custom controls , calender controls.. etc
will work as good as it worked in my system during design time

[si_the_geek]

If you do a proper installation, the VB runtimes and any additional things your program needs (such as ActiveX controls etc) will be setup appropriately, and will work as they did on your computer.

[make me rain]

If any valuable articles / tutorials will give me more knowledge , thanks for your help

[si_the_geek]

The FAQ thread at the top of this forum has links to several useful articles.

[dilettante]

Note that even items you late-bind have to be deployed to target computers if they are not standard system components (like the FSO, CDO For Windows, MSXML, ADO, etc.).

If the target systems are ancient enough (older than Win2K SP4 or so) you might need to deploy some of these!