Disadvantage?

What's the disadvantage of including all of the DLL's for a project with your installation package besides it being a large setup file?

:confused:

Maybe you should ask what is the disadvantage of NOT including all the .dlls .......

The disadvantage is your program might actually run, and those
who use it will see just how bad a programmer you actually are.
If you don't include them, the program will never run, and no one
will figure it out.

ROFL

I'll keep that in mind, thank you.

Originally posted by Thinker
The disadvantage is your program might actually run, and those
who use it will see just how bad a programmer you actually are.
If you don't include them, the program will never run, and no one
will figure it out.

Ouch.:eek:

Originally posted by VB_ACK
I'll keep that in mind, thank you.

You are welcome :D

I hope you took this in the spirit given. Your question was similar
to, "What will be the disadvantage if someone gives me a $100
bill?" Perhaps there is more to your question than was apparent
to those of us reading it?

Someone else proposed a similar question to that of mine. Asking whether or not they should include DLL's with their deployment package, but it was never answered.

I thought the application would run if it's using the already present DLL's on the user's system, if they exist that is.

The problem is, they often don't exist. Then your app doesn't run. And you look silly. Maybe that's not a big deal to you, but if my apps refuse to run often enough, I don't get to eat. I like to eat. My kids like to eat. My wife likes to eat. The dog likes to eat. So I have to include the dlls my apps require. Pretty simple logic. ;)

I think I got that reboot. :-\