Is it just me, or is this the biggest, most repetitive, most horribly
designed object model ever?  Does it really take 130+ classes to edit
some config files????

This really amazes me:
TimeSpanConverter
TimeSpanMinutesConverter
TimeSpanMinutesOrInfiniteConverter
TimeSpanSecondsConverter
TimeSpanSecondsOrInfiniteConverter
InfiniteTimeSpanConverter
It takes 6 separate classes to convert TimeSpan to text????


Or are these really necessary?
WhiteSpaceTrimStringConverter
SpecialSetting enum  (what's special about it?  some distinction the
developer missed in early design?)
SpecialSettingAttribute (read the help on that one)

ApplicationScopedSettingAttribute
UserScopedSettingAttribute
(what happened to the MachineScopedSettingAttribute?  they must have
forgotten that one)

The entire namespace is ridiculous.  130 classes to edit some text
files!!!  Only a kid right out of college with no experience could come
up with this crap.  The larger question is how did Microsoft let this
into the final product?

Using a different filename for App.config
.net memory leak problem in exe
formatting question
Monitoring ThreadPool threads?
Editor using Microsoft.mshtml assembly won't allow edit??