Configuration

[DarrellMozingo]

From @AnthonySteele (on the 7digital fork, which is now gone)...

We have an assembly called "Configuration" here. IMHO this isn't a very good name for a couple of reasons.

When you see "Configuration.dll" in the bin folder, it's hard to tell which reference it came from, or if it's in-house or from some third party kit. It's not a "world-configuration" library so it shouldn't be named as such.
When you reference it in code, it can easily clash with namespaces inside the project. it's hard to reference a namespace called "Configuration" in a class called .e.g. My.Api.Infrastructure.Configuration.ConnectionStringProvider you have to say global::Configuration otherwise the compiler assumes you mean your own parent namespace.
It's also really small and doesn't do much which is a design smell for a separate .dll.

This got a +1 from @knocte too.