There seems to be conflicting advice regarding which (including version) of DLL's to redistribute with an installation package.
I like the MS Windows Installer V1.1 but which DLL's etc should I distribute with my app and which one's should I "assume" are on the target machine?
That target system could be running an OS that has not yet even been released by MS. Example, if the package was built in (say) 2000 it may now want to be installed on XP.
Obviously, any "custom" OCX's etc are not a problem but what about the standard ones such as MSSTDFMT.DLL etc etc?
I noticed that Windows Installer 1.1 has the facility to install DLL's in the app folder and point the registry entries for the app at that folder so that the app (and only that app) will use those DLL's. Is that a good strategy?
Does anyone have a view as to which approach to take?
Alterntive strategies are most welcome.
Thanks Experts.
"Life is full of learning, and then there is wisdom"
I like the MS Windows Installer V1.1 but which DLL's etc should I distribute with my app and which one's should I "assume" are on the target machine?
That target system could be running an OS that has not yet even been released by MS. Example, if the package was built in (say) 2000 it may now want to be installed on XP.
Obviously, any "custom" OCX's etc are not a problem but what about the standard ones such as MSSTDFMT.DLL etc etc?
I noticed that Windows Installer 1.1 has the facility to install DLL's in the app folder and point the registry entries for the app at that folder so that the app (and only that app) will use those DLL's. Is that a good strategy?
Does anyone have a view as to which approach to take?
Alterntive strategies are most welcome.
Thanks Experts.
"Life is full of learning, and then there is wisdom"