.NET allows you to use .settings files to manage application settings. I would like to store Production, Development and Test settings separately in a way that I can do somethi
One thought is that switching between a series of static values sounds like a rather fraught way of doing things. I would suggest looking up the Singleton pattern. This pattern gives you a single class instance that is shared between all references to the class, but when it's first loaded you can do your normal initialisation bits to check your environment and set the values accordingly.
Equally, rather than using switches to act on different classes, wouldn't you be looking at designing one Interface, and having each class implement that interface?