Hi Barry,

I believe you may find your answer here:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/p
ersistappsettnet.asp

I have not done this, but from what I read, it seems that you can access the
ApplicationSettings via the Application class. The Application class is
public and static, so you should be able to do it.

You should not read exe's app settings directly from inside dll's code.

DLL, by its nature, is code module that seperates from exe code with
consideration that it could be used by other exes (of course that are other
reasons to use dll).
If you do the app.cofg reading inside dll code, you physically tie the dll
with certain exe, the dll's reuseability is go partially or completely, even
different version of the same exe may break the dll.

Of course you can make the dll to read some type of *.cofg/settings of
certain, or predefined format, say, you can assume there are always certain
settings exist and you would handle the absence of expeted but missing
settings properly. It sounds not elegent at all and I'd never do it, but you
can do it if insist. In this case, you only need pass a file path from the
calling exe app and do you file read, maybe (write) yourself.

Again, I'd never read user/app config in dll. If you need to process
information from *.config in the dll code, you can always read them from the
calling exe app and pass the data itself to a dll object to process it (and
return back the changed data and save to *.config by the exe). In your
example,

Properties.Settings settings =
MyNameSpace.Properties.Settings.Default;
MessageBox.Show(settings.MyProperty);

MyBOObject obj=new MyBOObject()

//assign setting value to the BO object
obj.Property1=setting.MyPropertiy

//Or process the setting value
obj.TheMethod(setting.MyProperty)