[ This article is for Windows Phone 8 developers. If you’re developing for Windows 10, see the latest documentation. ]
When implemented in a derived class, sets the URI scheme that specifies the transport used by the channel factories that are built by the bindings.
Assembly: System.ServiceModel (in System.ServiceModel.dll)
This user name for the binding is distinct from the specification of the protocol name, which is specified by the property. Each instance of a Binding has a Name and Namespace that together uniquely identify the user name for the binding in the metadata of the service. If you want to add more HTTP bindings, for example, you can name them whatever you want and set all of their schemes to "http". There is no inherent application or machine dispatch based on the . So you avoid the common problem of being unable to register additional handlers for well-known protocols. You can also easily work with multiple versions of a binding side-by-side by giving each version a different name.