WCF configuration file

WCF configuration file

 

The configuration file in the host application follows the same format as the configuration file in the client application. There is a <bindings> section where the bindings are defined and a <service> section in which the endpoints (addresses and bindings) are defined.

 

When defining endpoints in a configuration file the service name should be in the format of NAMESPACE.CLASSNAME, and the endpoint contract name should be in the format of NAMESPACE.INTERFACECLASS.

 

In the preceding example, the service namespace is WCFService with a class name of ServiceClass, and the interface is named IServiceClass. Therefore the service and endpoints are defined in the configuration file as the following:

 

<service name =”WCFService.ServiceClass”>

<endpoint contract =”WCFService.IServiceClass”

name=”NetTcpBinding_IServiceClass”

binding =”netTcpBinding”

address =”net.tcp://localhost:8000/TcpBinding”/>

<endpoint contract =”WCFService.IServiceClass”

name=”netNamedPipeBinding_IServiceClass”

binding =”netNamedPipeBinding”

address =”net.pipe://localhost/NetNamedPipeBinding”/>

</service>

 

 

 

posted @   Rickie  阅读(445)  评论(0编辑  收藏  举报
编辑推荐:
· Linux系列:如何用 C#调用 C方法造成内存泄露
· AI与.NET技术实操系列(二):开始使用ML.NET
· 记一次.NET内存居高不下排查解决与启示
· 探究高空视频全景AR技术的实现原理
· 理解Rust引用及其生命周期标识(上)
阅读排行:
· DeepSeek 开源周回顾「GitHub 热点速览」
· 物流快递公司核心技术能力-地址解析分单基础技术分享
· .NET 10首个预览版发布:重大改进与新特性概览!
· AI与.NET技术实操系列(二):开始使用ML.NET
· 单线程的Redis速度为什么快?
点击右上角即可分享
微信分享提示