Home > Advanced, C#, WCF > Undocumented parameters of the WCF Service Moniker

Undocumented parameters of the WCF Service Moniker

By looking at the .Net assemblies with Reflector, I have found parameters for the WCF service moniker that were not described in the documentation of Microsoft at the moment of writing this article. They can be found in the internal enum “System.ServiceModel.ComIntegration.MonikerHelper.MonikerAttribute”.

MonikerAttribute

I think that the meaning of each attribute should be pretty clear for people with WCF experience. All these attributes can be used as parameters for the WCF service moniker connection string.

  • Address: the address of the WCF service
  • Contract: the name of the contract of the WCF service
  • Wsdl: the complete WSDL of the WCF service
  • SpnIdentity: the expected Server Principal Name (SPN) identity of the WCF service endpoint.
  • UpnIdentity: the expected User Principal Name (UPN) identity of the WCF service endpoint. This is the logon name of the service on the network.
  • DnsIdentity: the dns (or the subject if the dns field is null) of an X.509 certificate used to authenticate the WCF service endpoint.
  • Binding: the binding of the WCF service
  • BindingConfiguration: the name of the binding configuration in the <appname.exe>.config file.
  • MexAddress: the MEX address of the WCF service
  • MexBinding: the MEX binding type of the WCF service
  • MexBindingConfiguration: the name of the mex binding configuration in the <appname.exe>.config file.
  • BindingNamespace: The binding name space of the WCF service.
  • ContractNamespace: The contract name space of the WCF service.
  • MexSpnIdentity: the expected Server Principal Name (SPN) identity of the MEX endpoint of the WCF service
  • MexUpnIdentity: the expected User Principal Name (UPN) identity of the MEX endpoint of the WCF service. This is the logon name of the service on the network.
  • MexDnsIdentity: the dns (or the subject if the dns field is null) of an X.509 certificate used to authenticate the MEX endpoint of the WCF service.
  • Serializer: the serializer to use (the DataContract serializer or the old XML serializer)
Advertisements
Categories: Advanced, C#, WCF
  1. chris
    April 20, 2011 at 19:04

    Thanks. that explains the COM moniker.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: