Decouple WCF Service Proxy Classes From Environment Endpoints

I have a WCF Service, I won't waste anyone's time with copy/pasting a basic implementation here, just imagine it as being the standard "Echo" example you see scattered around MSDN. Let's say I host the Service Library using IIS / a web app. Let's also say I publish the website to varying environments, local, shared dev server, varying test servers, and of course varying live environments. We'll also assume that the WCF gods smiled down upon us and the deployments went without a hitch.

Now I want to write an app (lets say WPF app for some clarity). When the app starts, I want a drop down listing all the available environments. I don't mind hard-coding or supplying (by means of a config file) those environments, but kudos points for linking any articles showing LAN discovery of deployed WCF services?

When the user has selected their chosen environment, I want the app to be able to call a method on the service (in the correct environment). Now I could do this with a big select case/if statement, instantiating the appropriate proxy class for the environment selected, calling out using the proxy class, etc. I could even pass the class around from method to method as an object and then use select case/if statements alongside TryCast/DirectCast to ascertain which environment the provided proxy class belongs to.

I'm bordering on the idea of selecting an environment (none in particular, just one of them) and on the assumption that all deployments/environments have identical code, instantiate the proxy client with the endpoint details of my chosen environment. I lose a form of type safety, but is that ok? Is that the done way?