3 replies to this topic

[rags33]

I have a dll A and I call functions within the dll A. This dll A uses another dll B. When I try to load A it fails. I have both A & B in the same directory.

When I look into dependencies IS is trying to load dll B from c:\winnt\system32? Why????

[Taco Bell]

Well that (system32) is in the path, but I'm not sure why it's using that.  I would think the local directory would take precedence.  I've not worked loading DLLs under IS though, so I really have no idea.  Sorry.

(Edited by TacoBell00 at 9:29 pm on Jan. 16, 2002)

[KathyMorey]

I haven't done this with dependent dll's personally, but I seem to remember discussion about using ChangeDir first to make sure that the directory the dll's are in is the current directory.

HTH
Kathy

[clvrmnky]

UseDLL() will not find shared DLLs in the same directory.  DLLs are found in one of three ways:

1. In the "current directory"
2.In the standard system areas
3. on the PATH environment

To make sure your install works without depending on the PATH, and for a DLL that is not in WINSYSDIR, do one of the following:

1. Use ChangeDirectory() to make the current working directory the same as where the shared DLL lives.  i.e.: ChangeDirectory(SUPPORTDIR).

2. Load the DLL in the right order.  That is, if you have A.dll that depends on B.DLL, then you would:

UseDLL("B.DLL");
UseDLL("A.DLL");
[...]
UnuseDLL("A.DLL");
UnuseDLL("B.DLL");

If you have further need of exported function calls, you would call that DLL first, and so on.

Both methods work for me, but (1) seems more robust.  Having the CWD set to SUPPORTDIR does not seem to affect the install's cleanup at the end of the process.