Re: mfc ext dll from path
Like the article said this is the order in which the OS looks for a dll that
your app is trying to load. You can always give #6 a try (add your dll's
path to the PATH variable)
1.. The directories listed in the App Path registry key
2.. The directory where the executable module for the current process is
located.
3.. The current directory.
4.. The Windows system directory. The GetSystemDirectory function
retrieves the path of this directory.
5.. The Windows directory. The GetWindowsDirectory function retrieves the
path of this directory.
6.. The directories listed in the PATH environment variable.
AliR.
".rhavin grobert" <clqrq@yahoo.de> wrote in message
news:1188230616.276786.129920@k79g2000hse.googlegroups.com...
On 27 Aug., 17:42, "AliR \(VC++ MVP\)" <A...@online.nospam> wrote:
I have never tried this but it might work. Specifing the application/dll
path in the registery.
http://www.codeguru.com/Cpp/W-P/dll/article.php/c99
that one really has a sour taste;-\ i'd like to leave the registry
untouched by all of my programms exept for adding filetypes. isn't
there a straitforward way to say: "you find foo.dll at './subdir/
foo.dll' ", relative to the current path?
that way, anyone could put my app in a directory he wants and just has
to provide the subdirectory-structure as is. you could even move the
app-folder after installation to $whereever and still it would run
fine...