This is a tricky one to try to explain in 100 words or less, but here goes...

Our middle-tier has several layers to it, with a front-man called an application manager. We use a remoting service [basic remoting framework, written in C#] so that our Web Service can 'remote' with the middle-tier, which may reside on a different server.

The problem is that some of the DLLs in the middle-tier need to open a configuration file [client settings stored in XML]. We'd like to store this XML config file in the same folder where the middle-tier DLLs reside. Unfortunately, because the main front-man for the middle tier is accessed via 'remoting', the default folder is usually something like C:\WINNT\SYSTEM32 [since we run the remoting server as a service].

So by the time any middle-tier DLL function gets 'called' [via remoting], the code executing in the DLL doesn't seem to be able to 'know' the folder where it actually resides on disk [again, the value of that info would be so that we can place an XML config file in the same folder, so that a READXML could specify the file name without having to specify a drive letter and path].

Any thoughts on how to get around this [so that a DLL that's executing through 'remoting' can still gain access to the folder name where it's stored]?

Thanks,
Kevin