Printable View
I see you're not supposed to install your DLL's on other machines, however this is how I got around a problem I couldn't solve any other way. I have tested it and the testing machine works great afterwards, however I am wondering about possible effects, long term or if it works right afterwards, all is well?
Please shed some light on this.
Thanks.
Actually, I think you need to shed some light.... "I see you're not supposed to install your DLL's on other machines -- why the heck not? How else would the application work? Where did this "rule" come from?Quote:
Originally posted by NicePackage
I see you're not supposed to install your DLL's on other machines, however this is how I got around a problem I couldn't solve any other way. I have tested it and the testing machine works great afterwards, however I am wondering about possible effects, long term or if it works right afterwards, all is well?
Please shed some light on this.
Thanks.
TG
phreak, I checked out that link. That's dealing with OCX's and it seems there's no warning about those within ********** or inno setup. If there is, it didn't concern me at the time.
TG, in ********** it says the DLL's aren't found, unless I put a copy of them someplace other than the system directory. If I spoon feed the location in the script while running inno setup I get:
**************
Attempt to deploy DLL file from own Windows System directory.
See the "Unsafe Files" topic in the help file for more information on why this is dangerous and should be avoided.
**************
So I go check out the help, this is an exerpt of what I found.
**************
You should not deploy any DLLs out of your own Windows System directory because most of them are tailored for your own specific version of Windows, and will not work when installed on other versions. Often times a user's system will be rendered unbootable if you install a DLL from a different version of Windows. Another reason why it's a bad idea is that when you install programs on your computer, the DLLs may be replaced with different/incompatible versions, and were you not to notice this and take action, it could also lead to problems on users' systems when you build new installations.
**************
Hopefully now I have made myself more clear as to why I am questioning deploying the DLL's from my development system.
Thank you.
you "are" supposed to put the systems files (DLL/OCX/ect..) in an install or resource directory. THen have INNO pull them from there..
That warning os for your own protection..
Just to have it right.
What you need to do is create a 'resource' directory, copy the necessary dll, ocx, etc files from the windows directory and go from there.
Is that it? Just copy the files and you are fine?
Thanks,
JB
why don't you tell us what DLLs your app needs because that is what really matters when it comes to what dlls you should and should not include...
also for installing the VB runtimes.. download the self extracting executable from MS that installs the runtimes.. you can include it in your INNO setup and execute it via the [run] section with a /q param so it does it silently.
this ensures the runtimes are installed properly and not just copied and registered
I appreciate the info!
Take care,
JB