Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It sounds like the "filepath" it is expecting may be relative to the working directory, or the working directory or even the application directory is important to the dll. </p> <p>That dll may also try to reference other dll's in its directory, but can't find them because it was loaded from its own folder instead of the exe running in its directory.</p> <p>About half way down <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ms682586%28v=vs.85%29.aspx#search_order_for_desktop_applications" rel="nofollow">this page</a> it describes the search order for dll resolution:</p> <blockquote> <ol> <li><p>The directory from which the application loaded.</p></li> <li><p>The current directory.</p></li> <li><p>The system directory. Use the GetSystemDirectory function to get the path of this directory.</p></li> <li><p>The 16-bit system directory. There is no function that obtains the path of this directory, but it is searched.</p></li> <li><p>The Windows directory. Use the GetWindowsDirectory function to get the path of this directory.</p></li> <li><p>The directories that are listed in the PATH environment variable. Note that this does not include the per-application path specified by the App Paths registry key. The App Paths key is not used when computing the DLL search path.</p></li> </ol> </blockquote> <p>Hope that helps.</p> <p>EDIT: Another idea... You could go and write a wrapper for that DLL so that it returns the correct values, and make an interface that works with your unit tester built into your wrapper.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload