I have a suggestion for the Framework guys:

It would be nice to have a "default config" similar to Machine.config that
can more easily be deployed than merging my "default.config" with the
machine's machine.config

For instance, I'd like to add some deafult settings for my class library...
only way to do that is to either embed my default settings in the
machine.config or somehow encourage the users of the library to merge my
config into theirs... not very graceful...

I suggest moving to a more broken up format, whereas each Assembly's
FullName gets a config file:
System.Web, Version=1.1.4322, PublicKeyToken=XXXXXXXX.config
System.Web.Services, Version=1.1.4322, PublicKeyToken=XXXXXXX.config

and so forth, then I can do mine without merging:

Ensoft.DataComponents, Version=1.0.1000, PublicKeyToken=XXXXXXX.config

i still like the machine.config idea, but its become just like the
registry... one big area that could easily become corrupt through just one
bad character. Anyhow, thats my suggestion... maybe we'll see it in
Framework 2.0? I can only dream!

--
Eric Newton
C#/ASP Application Developer
http://ensoft-software.com/
eric@cc.ensoft-software.com [remove the first "CC."]