Thread: Problems running compiled .exe on other machines.

I assure you that you are perfectly capable of avoiding DLL by doing the following:

- If your program has dependencies, check them.
- If you can avoid using COM objects that need registering, do so.
- If you do any sort of update whatsoever, always unregister, then reregister COMs.
- Simply putting a get_version() or similar function in the library, and checking its return.

I would put avoid using .NET framework in the list, but seeing as that it will surely result in flaming, I won't. Really the main thing is the last point on my list. Naming them is a great idea, right? Wrong! Believe it or not, the above average user will think they can get rid of those nasty start-up errors by simply renaming the DLL to match whatever your program argues is "missing." Users are unpredictable. Never forget that.

Originally Posted by master5001

Naming them is a great idea, right? Wrong! Believe it or not, the above average user will think they can get rid of those nasty start-up errors by simply renaming the DLL to match whatever your program argues is "missing." Users are unpredictable. Never forget that.

absolutely right 5001
i have done exactly that, many times, but can not remember how many times i could get it to work correctly.

i like one thing about .dlls that, if found in the same folder as .exe, then, the program runs just fine.

it is literally dll-hell!!
i just hope that situation is improved now

now i figure why those silly errors would come up:
i had a program that would use some common msvc .dlls, but, i would put the needed dll with the program installer, that would put them in the same folder as the program. But. when the installer was run to uninstall my program, then, some times, it would report error (installer), saying that, one or more apps need to be closed, before uninstall could continue.