 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
gandalf Guest
|
Posted: Mon Apr 24, 2006 8:03 pm Post subject: Deploying Indy with SSL dlls |
|
|
Using.....
D2005
Win XP SP2
Indy 10.0.20
libeay32.dll
ssleay32.dll
Hi,
I am coming up against a problem related to how various versions of Windows
search for DLLs , or at least I think that is the problem.
I am developing on XP SP2 and am testing deployment.
I am using Indy and as the App needs SSL I have the 2 DLLs it needs in the
same directory as the application exe.
On all my XP SP2 machines the deployment is fine. However, when the target
machine is running XP SP1 the DLL search path seems to be forced straight to
the Windows\System32 directory, where some other app has put the same (same
name but different content) DLLs. My App doesn't like those DLLs and fails.
(I can't actually get my paws on the target machine as it is in a distant
location so I don't know yet what app is also using the SSL dlls)
I don't want to simply overwrite the existing DLLs with my DLLs as that is
just going to cause my App to work while screwing up whatever App is
currently using them. Not an acceptable route.
As this 'problem' must have surfaced many times I ask for your input as to
the best strategy to adopt to resolve this.
Thanks
John |
|
| Back to top |
|
 |
MikeR Guest
|
Posted: Tue Apr 25, 2006 1:03 pm Post subject: Re: Deploying Indy with SSL dlls |
|
|
gandalf wrote:
| Quote: | Using.....
D2005
Win XP SP2
Indy 10.0.20
libeay32.dll
ssleay32.dll
Hi,
I am coming up against a problem related to how various versions of Windows
search for DLLs , or at least I think that is the problem.
I am developing on XP SP2 and am testing deployment.
I am using Indy and as the App needs SSL I have the 2 DLLs it needs in the
same directory as the application exe.
On all my XP SP2 machines the deployment is fine. However, when the target
machine is running XP SP1 the DLL search path seems to be forced straight to
the Windows\System32 directory, where some other app has put the same (same
name but different content) DLLs. My App doesn't like those DLLs and fails.
(I can't actually get my paws on the target machine as it is in a distant
location so I don't know yet what app is also using the SSL dlls)
I don't want to simply overwrite the existing DLLs with my DLLs as that is
just going to cause my App to work while screwing up whatever App is
currently using them. Not an acceptable route.
As this 'problem' must have surfaced many times I ask for your input as to
the best strategy to adopt to resolve this.
Thanks
John
John - |
MS has a strategy called side-by-side. Here are a couple of links to start you
off. Google for more....
http://www.pbdr.com/ostips/dllside.htm
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsetup/html/dlldanger1.asp
Mike |
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|