treyjeff
asked on
Smaller Setup Files?
I made a very very simple program that I want to send to friends but they are always missing the VB run time files. Is there a way to make a file where I can just send it out? I don't want them to HAVE to run a setup program.
VB programms required run time files they don't use the compiler like C++ where you don't need it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'd give you both marks but can only give one. That quite frankly sucks about VB :)
Well it does and it doesn't. Yes, it's a PITA that you can't just ship a .EXE file out and expect it to run on a "cold" install, but there is a method to their madness.
You see by sending the .DLL's along with the app you can be sure that the target system gets the correct support files no matter what particular flavor of windows they have. The SETUP.EXE program is smart enough NOT to overwrite the files on the target system if the target has newer versions.
Also, if you compiled everything into one (gonna be HUGE) .EXE then you essentially "freeze" the program with the configuration on *your* development box. This would limit printer selections, etc. By shipping the .DLL's seperately the .EXE size is kept wayyyy down and if the target system gets new stuff over the development box, your software automatically gets the enhancements too. No recompiling, no fiddling.
This allows the OS to grow and all the programs to track right along with it. This is part of M$'s "infinitely extensibly" OS design concept. It's a good idea, occassionally poorly implemented.
M
You see by sending the .DLL's along with the app you can be sure that the target system gets the correct support files no matter what particular flavor of windows they have. The SETUP.EXE program is smart enough NOT to overwrite the files on the target system if the target has newer versions.
Also, if you compiled everything into one (gonna be HUGE) .EXE then you essentially "freeze" the program with the configuration on *your* development box. This would limit printer selections, etc. By shipping the .DLL's seperately the .EXE size is kept wayyyy down and if the target system gets new stuff over the development box, your software automatically gets the enhancements too. No recompiling, no fiddling.
This allows the OS to grow and all the programs to track right along with it. This is part of M$'s "infinitely extensibly" OS design concept. It's a good idea, occassionally poorly implemented.
M