Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think you need to provide more information. There are so many approaches at persisting configuration information. We don't even know the development platform. .Net?</p> <ol> <li><p>I wouldn't rely on the registry unless I was sure it would always be available. You might get away with that on client machines, but you've already mentioned webservices.</p></li> <li><p>XML file in the current directory seems to be very popular now for server side third-party dlls. But those configurations are optional.</p></li> <li><p>If this is ASP, Your <a href="http://msdn.microsoft.com/en-us/library/ms998341.aspx" rel="nofollow noreferrer">Trust Level</a> will be very important in choosing a configuration persistance method.</p></li> <li><p>You may be able to use your Application server's "Application Scope". Which gets loaded once per lifetime of the application. Your DLL can invalidate that data if it detects it needs too.</p></li> <li><p>I've used text files, XML files, database, various IPC like shared memory segments, application scope, to persist configuration information. It depends a lot on the specifics of your project.</p></li> </ol> <p>Care to elaborate further?</p> <p>EDIT. Considering your clarifications, I'd go with an XML file. This custom XML file would be loaded using a search path that has been predefined and documented. If this is ASP.Net you can use Server.MapPath() for example to check various folders like App_Data. The DLL would check the current directory for the configuration file first though. You can then use a "manager" thread that holds the configuration data and passes it to any child threads that require it. The sharing can use IPC like a shared memory segment.</p> <p>This seems like hassle, but you have to store the information in some scope... Either from disk, memory ( application scope, session scope, DLL global scope, another process/IPC etc. )</p> <p>ASP.Net also gives you the ability to add <a href="http://aspnet.4guysfromrolla.com/articles/020707-1.aspx" rel="nofollow noreferrer">custom configuration sections</a> to standard configuration files like web.config. You can access those sections at will and they will not depend on when your DLL was loaded.</p> <p>Why do you believe your DLL is being removed from memory? </p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload