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.
LVL 1
treyjeffAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MarineCommented:
VB programms required run time files they don't use the compiler like C++ where you don't need it.
0
mark2150Commented:
You have no choice. You'll have to build a setup and have them run it at least once. After they've installed it the first time you can just send them the .EXE as you make changes. If you add a new control that requires additionall .DLL's or .OCX's  you'll have to rebuild the SETUP and install again.

Sorry. This is how it works by design.

M
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
treyjeffAuthor Commented:
I'd give you both marks but can only give one.  That quite frankly sucks about VB :)
0
mark2150Commented:
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
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.