Best way for a dll to get configuration information? -

we have developed number of custom dll's called third-party windows applications. these dlls loaded / unloaded required.

most of dlls call web services , these need have urls, timeouts, etc configured.

because dll not permanently in memory, has read configuration every time invoked. seems sub-optimal me.

is there better way handle this?

note: configurable information in xml file department can alter required. not accept registry edits.

note: these dll's cater number of third-party applications, esentially implements external edms interface. vendors not accept passing required parameters.

note: it’s a.net application , dll written in c#. essentially, there both thick (windows application) , thin clients access dll when need perform kind of edms operation. edms interface defined set of calls have implemented in dll , dll decides how implement edms functions e.g. clients, “register document” update db , others same call utilise third-party edms system. there no asp clients.

my understanding dll loaded when client wants access edms operation , unloaded when call finished. client may not need edms operation while (in cases on hour).

use registry store configuration information, it's fast enough.