Edit

<standardEndpoints>

  • Article

This configuration section allows you to define a collection of standard endpoints, which are reusable preconfigured endpoints. A standard endpoint will have one or more of the address, binding and contract attributes set to a fixed value. For example, in the discovery endpoint the contract is fixed. You can also use standard endpoints to extend service endpoint with new properties similar to defining custom bindings.

<configuration>
  <system.serviceModel>
    <standardEndpoints>

Syntax

<system.serviceModel>
  <standardEndpoints>
  </standardEndpoints>
</system.serviceModel>

Attributes and Elements

The following sections describe attributes, child elements, and parent elements.

Attributes

None.

Child Elements

Element Description
<announcementEndpoint> Defines a standard endpoint with a fixed announcement contract. A service can optionally announce its availability by sending an online and offline announcement message when it is opened or closed respectively. A Windows Communication Foundation (WCF) service specifies the announcement endpoints in the <serviceDiscovery> element and uses the AnnouncementClient to perform the announcements. A client wishing to listen for the announcement from other service is actually acting as a WCF service; thus you have to configure the announcement endpoints for that client in the <services> section.
<discoveryEndpoint> Defines a standard endpoint with a fixed discovery contract. When added to the service configuration, it specifies where to listen for the discovery messages. When added to the client configuration it specifies where to send the discovery queries.
<dynamicEndpoint> This configuration element defines a standard endpoint that contains information to enable an application to function as a client program that can find the endpoint address dynamically at run time.
<mexEndpoint> Defines a standard endpoint with a fixed IMetadataExchange contract. Since all metadata exchange endpoints specify IMetadataExchange as their contract, you can use this standard point instead of defining one for yourself.
<udpAnnouncementEndpoint> Defines a standard endpoint that is used by services to send announcement messages over a UDP binding. It has a fixed contract and supports two discovery versions. In addition it has a fixed UDP binding and a default address value as specified in the WS-Discovery specifications (WS-Discovery April 2005 or WS-Discovery version 1.1). You can specify the multicast address to use for sending and receiving the announcement messages.
<udpDiscoveryEndpoint> Defines a standard endpoint that is pre-configured for discovery operations over a UDP multicast binding. This endpoint has a fixed contract and supports two WS-Discovery protocol versions. In addition, it has a fixed UDP binding and a default address as specified in the WS-Discovery specifications (WS-Discovery April 2005 or WS-Discovery V1.1).
<webHttpEndpoint> Defines a standard endpoint with a fixed <webHttpBinding> binding that automatically adds the <webHttp> behavior. Use this endpoint when writing a REST service.
<webScriptEndpoint> Defines a standard endpoint with a fixed <webHttpBinding> binding that automatically adds the <enableWebScript> behavior. Use this endpoint when you are writing a service that is called from an ASP.NET AJAX application.
<workflowControlEndpoint> Defines a standard endpoint for controlling the execution of workflow instances (create, run, suspend, terminate, etc).

Parent Elements

Element Description
<system.ServiceModel> The root element of all WCF configuration elements.

See also