Hi,
I need to have a windows service that can access various DLL's dynamically.
These dll's are stored in a particular directory, but of course this can
vary by application.
The problem is that when the windows service runs, it actually runs from
c:\windows, not from the location of the actual executable. Now, for a
regular windows app, I would have a configuration file, that tells the
executable additional directories to check when looking for DLL's.
However, since the configuration file is in some other directory other then
c:\windows, the windows service doesn't read it.
So, what is a way to get the windows service to either:
a) be capable of reading it's config file on start up, such that it can
check other directories (which are a relative path from the location of the
executable)
b) another way for the executable to automatically look in other folders
(relative path) when looking for DLL's?
