John:
Thank you for this information. But of course I have some questions if you
would be so kind.
Would I simply add a normal "settings / configuration" file to the .dll like
I would to an .exe? But how would I make the constructor take this
configuration file? Would you happen to have a link that would demonstrate
this, as I understand the concept, but not sure how to implement it as this
sounds like a very definiate solution to our problem.
"John Sun" wrote:
You can also design an constructor which takes a configuration file.
When the object is initialized with this constructor, you can set up
all the properties.
HTH
Andy wrote: Would using the Machine.Config file work for universal things such as a
database connection?
"Andy" wrote:
Is it possible to use a Settings / Configuration file in VS 2005 / .Net 2.0
in a dll? Or is this feature limited to an executable?
We have some .dlls where a configuration file would be helpful for things
such as Database Connection and other aspects. But when we use this file and
try to access it using Properties.Settings.Default....., we get an object
error.
If this is possible: what are we doing wrong?