Hello All,
I wish to deploy a project with packages. Some component libraries, such as
Elpack and TMS components, don't put the version number in the package
names
so I am afraid for version conflicts (DLL hell) if I put these into the
system32 directory.
My idea is to put the packages into a private directory (\program
files\my company
packages) and to make registry entries for all my applications in
HKLM\Software\Microsoft\Windows\Currentversion\App Paths so all my
executables
will share a common packages directory.
My questions:
- Does this "app paths" trick actually work with Delphi apps and packages?
- Is this path appended or pre-pended to the application's path?
- Is its function operating system dependant?
- Some of my apps aren't executables (processes) at all, they are
ActiveX DLL's.
Will this principle work for those as well?
--
Arthur Hoornweg
(In order to reply per e-mail, please just remove the ".net"
from my e-mail address. Leave the rest of the address intact
including the "antispam" part. I had to take this measure to
counteract unsollicited mail.)
