IIS Express does not have the NET.TCP binding feature, local testing can only be hosted using native IIS, and requires the appropriate configuration (see previous article).
 
Forget it, just give a configuration example, too lazy to write ...
 
<System.ServiceModel>    <Bindings>      <BasicHttpBinding>        <!--the configuration of the default HTTP binding, which increases the size of the maximum transfer information, if you do not need to set the binding configuration -        <bindingname= "Defaultbasichttpbinding"maxBufferSize= "10485760"MaxReceivedMessageSize= "10485760" />      </BasicHttpBinding>      <nettcpbinding>        <!--The default net.tcp binding configuration, it seems necessary to configure the net.tcp mode binding -        <bindingname= "Defaultnettcpbinding"portsharingenabled= "true"Transfermode= "Buffered">          <SecurityMode= "None" />        </binding>      </nettcpbinding>    </Bindings>    <Behaviors>      <servicebehaviors>        <Behavior>          <!--to avoid leaking metadata information, set the following values to false before deployment -          <Servicemetadatahttpgetenabled= "true"httpsgetenabled= "true" />          <!--to receive the fault exception details for debugging, set the following value to True. Set to false before deployment to avoid leaking exception information -          <ServicedebugIncludeexceptiondetailinfaults= "true" />        </Behavior>      </servicebehaviors>    </Behaviors>    <Services>      <Servicename= "Wcftest.dataservice">        <!--Endpoint Address attribute: 1, use absolute path (URL), 2, if use relative path (URL), will determine final path (URL) according to host's baseaddress.  -                <!--http Binding Method -        <EndpointAddress=""binding= "BasicHttpBinding"Contract= "Wcftest.idataservice"bindingconfiguration= "Defaultbasichttpbinding" />        <!--Net.TCP Binding Method -        <EndpointAddress=""binding= "NetTcpBinding"Contract= "Wcftest.idataservice"bindingconfiguration= "Defaultnettcpbinding" />        <!--The Metadata Exchange (MEX) endpoint is used by the appropriate service to introduce itself to the client. This endpoint does not use secure bindings and should be secured or removed before deployment -                <!--providing metadata for HTTP bindings -        <EndpointAddress= "Mex"binding= "mexHttpBinding"Contract= "IMetadataExchange" />        <!--providing metadata for net.tcp bindings -        <EndpointAddress= "Mex"binding= "Mextcpbinding"Contract= "IMetadataExchange" />                <!--the base address that hosts the WCF service.        Note: When you use an ASP. NET Web site to host a WCF service, the Web site needs to use the Svc file to host the service, where the base address becomes the location of the Svc file.  -        <Host>          <baseaddresses>            <Addbaseaddress= "http://localhost/Design_Time_Addresses/DataService/" />          </baseaddresses>        </Host>      </Service>    </Services>  </System.ServiceModel>