> What is your suggestion to deal best with .Net 2.0 configuration for a DLL
> assembly (outside every application)?
> The DLL should handle the configuration itself.
>
> Thanks for your effort!
If you derive from ApplicationSettingsBase your dll can load and save app
settings at the user level. Your DLL components can also derive the
IPersistComponentSettings interface.
Usually, however, I let the application decide how to configure the DLL
properties and document the configuration available.

Signature
Doug Semler, MCPD
a.a. #705, BAAWA. EAC Guardian of the Horn of the IPU (pbuhh).
The answer is 42; DNRC o-
Gur Hfrarg unf orpbzr fb shyy bs penc gurfr qnlf, abbar rira
erpbtavmrf fvzcyr guvatf yvxr ebg13 nalzber. Fnq, vfa'g vg?
If the Dll is referenced by the launching executable, it should have access
to the configuration settings that were read when the application started,
provided it has a reference to System.Configuration. Have you tried this?
-- Peter
Recursion: see Recursion
site: http://www.eggheadcafe.com
unBlog: http://petesbloggerama.blogspot.com
BlogMetaFinder: http://www.blogmetafinder.com
> What is your suggestion to deal best with .Net 2.0 configuration for a DLL
> assembly (outside every application)?
> The DLL should handle the configuration itself.
>
> Thanks for your effort!