- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This sounds easy enough to fix but has been very perplexing. All symbols resolve. I explicitlysetthe dependency path in the calling program, and the "Addional Depency" lib is also correct. When I run the calling program, it starts, but then complains about not finding the DLL. I cannot be more explicit. So I placed the DLL in the same directory as the .exe and it runs there OK. Just wondering if there is some option or property setting that does not allow the exe to find it if its not in its own directory. I've tried both relative and absolute paths.
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The dependency path is of limited usefulness and I suggest not using it. DLLs should be in one of the standard places Windows will look for them, including the current directory, the directory containing the EXE, the Windows folder, the Windows System folder and folders mentioned in PATH.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Steve Lionel (Intel)
The dependency path is of limited usefulness and I suggest not using it. DLLs should be in one of the standard places Windows will look for them, including the current directory, the directory containing the EXE, the Windows folder, the Windows System folder and folders mentioned in PATH.
OK I did not know about the limited usefulness of the dependency path. So I should make the output path
of the DLL be the path of the EXE so I dont have to copy it after each rebuild. When its installed on user PC it will be there anyway. Got it, thanks.

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page