-
I have an application that has only four files. All four files are to be placed in the C:\WINDOWS\System\ dir. I tried using the setup wizard that comes with VB% Enterprise edition and it ended up making the install file with 15, that's right 15 additional install files to go along with my necessary 4 files. Now to me, that really is bothersome.
Either I don't know how to use the setup wizard properly or I need a better way to create a setup wizard/install exe...
Any Ideas?
-
The setup wizard includes all files needed to run your app on a machine with no previous installation of your app eg it has included VB runtime dll's and any control ocx's etc.
-
I personally suggest to include only the primary needed files, generally windows machines have already less recent versions of VB.
For exemple, I normally include VB6, mscomdlg.ocx and comdlg.ocx as these always present registration problems within windows.
I usually get up to 7 files.
-
That's not that much.
Your program doesn't only need the ocx you see in you're project. It also needs things like the vb runtime.
If you're using any databound controls, some DAOxxx.dll will be necessary, If you're using crystal reports you will need more dll's, The setup program itself needs several dll's in order to run, etc. etc.
The setup wizards scans the dependencies and includes everything, making sure nothing will be missing on the target machine.
15 files isn't that much. The files in the bootstrap part of setup.lst (usually about 10) will be deleted after setup finishes.
-
Well I always believed the less files involved, the less chance for errors...
This is a Winsock chat program, very limited, only really needs the four files...but if you believe that the extra files are ok, I will try it out.
I just wanted to know if this was usual or not, thankyou all.
