I agree with the namespace conflict. The word "Settings" would tend to make me nervous as a class name, because I would expect it to be used too often. In general, I want names to be descriptive (as that one certainly is), but complicated enough to be unique. After all, thanks to intellisense, you generally don't have to type more than a few characters. Therefore, you could use something like ProjectSettings, or even ProjectSettingsForThisHereDifferentKindOfProject (actually, there is probably a name length limit, but I don't know what it is).


That's the only CAPITAL error I see. Is there more?