blocks|key|1413166|text|为了使用ChannelFactory<T>，您必须愿意在服务和客户端之间共享契约程序集。如果您对此没有意见，那么ChannelFactory<T>可以为您节省一些时间。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1413167|entityMap^0|4|H|1K|H|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

Well in order to use <code>ChannelFactory&lt;T&gt;</code> you must be willing to share contract assemblies between the service and the client. If this is okay with you then <code>ChannelFactory&lt;T&gt;</code> can save you some time.

blocks|key|1197923|text|代理将构建异步函数，这对它来说是很好的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1197924|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The proxy will build async functions for which is kind of nice.

blocks|key|1197992|text|我在使用MetadataResolver.Resolve方法的同时使用ChannelFactory。客户机配置很麻烦，所以我从服务器获取ServiceEndpoint。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1197993|当您使用ChannelFactory(Of+T)时，T是您可以从项目中的引用中获得的原始合同，也可以是生成的合同实例。在某些项目中，我从服务引用生成代码，因为我无法添加对契约dll的引用。您甚至可以生成一个带有服务引用的异步约定，并将该约定接口与ChannelFactory一起使用。|1197994|对我来说，使用ChannelFactory的主要目的是去掉客户端配置信息。在下面的示例代码中，您可以看到如何在没有配置的情况下实现WCF客户端。|1197995|Dim+fixedAddress+=+"net.tcp://server/service.svc/mex"
Dim+availableBindings+=+MetadataResolver.Resolve(GetType(ContractAssembly.IContractName),+New+EndpointAddress(fixedAddress))
factoryService+=+New+ChannelFactory(Of+ContractAssembly.IContractName)(availableBindings(0))
accesService+=+factoryService.CreateChannel()|code-block|syntax|javascript|1197996|在我的最终项目中，检查availableBindings以使用net.tcp或net.pipe+(如果可用)。这样，我就可以使用最好的可用绑定来满足我的需求。我只依赖于服务器上存在元数据端点这一事实。|1197997|我希望这能帮到你|1197998|顺便说一句，这是使用.NET+3.5完成的。然而，它也适用于4.0。|1197999|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|V|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

I use ChannelFactory along with MetadataResolver.Resolve method. Client configuration is a bother, so I get my ServiceEndpoint from the server. 

When you use ChannelFactory(Of T), T is either the original contract that you can get from a reference in you project or a generated contract instance. In some projects, I generated the code from a Service Reference because I could not add a reference to the contract dll. You can even generate an asynch contract with the service reference and use that contract interface with ChannelFactory.

The main point of using ChannelFactory for me was to get rid of the WCF client config information. In the sample code below, you can see how to achieve a WCF client without config.

<pre><code>Dim fixedAddress = "net.tcp://server/service.svc/mex"
Dim availableBindings = MetadataResolver.Resolve(GetType(ContractAssembly.IContractName), New EndpointAddress(fixedAddress))
factoryService = New ChannelFactory(Of ContractAssembly.IContractName)(availableBindings(0))
accesService = factoryService.CreateChannel()
</code></pre>

In my final project, the availableBindings are checked to use net.tcp or net.pipe if available. That way, I can use the best available binding for my needs. I only rely on the fact that a metadata endpoint exist on the server.

I hope this helps

BTW, this is done using .NET 3.5. However it does work also with 4.0.

blocks|key|1198066|text|我的答案是对Keith's和Andrew+Hare's答案的一种总结。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1198067|如果您不控制服务器，而只有WSDL/URL-使用Visual+Studio或svcutil生成代理。(请注意，当svcutil工作得更好时，Visual+Studio有时会失败)。|1198068|当您同时控制服务器和客户端时，共享接口/契约并调用ChannelFactory|1198069|。|1198070|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/2583403/52277|1|https://stackoverflow.com/a/1698293/52277^0|6|7|0|E|D|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]|$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|11|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]|R|$5|M|N|O|C|$P|S]]]]

My answer is a kind of summary of <a href="https://stackoverflow.com/a/2583403/52277">Keith's</a> and <a href="https://stackoverflow.com/a/1698293/52277">Andrew Hare's</a> answers. 

If you do not control server, but have only WSDL/URL- generate proxy using Visual Studio or svcutil. (Note that Visual Studio sometimes failed, when svcutil works better).

When you control both server and client, share interfaces/contracts and call ChannelFactory 
.

blocks|key|1413416|text|这不仅仅是节省时间的问题。使用WSDL生成的代理是危险的，因为如果忘记更新服务引用，可能会使解决方案处于不一致的状态。一切都被编译了，但是服务契约被破坏了。我强烈建议只要有可能就使用ChannelFactory，这样会让你的生活更轻松。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1413417|一种可能的替代方案是编写一个预构建脚本，该脚本在每次构建项目时调用SVCUtil实用程序来创建代理，但不管怎样，ChannelFactory要整洁和优雅得多。|1413418|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

It's not just a matter of time saved. Using the WSDL generated proxy is dangerous because if you forget to update the service reference you can leave the solution in an inconsistent state. Everything compiles but the service contract is broken. I definetly suggest to use a ChannelFactory whenever possible, you make your life much easier.

A possible alternative could be to write a prebuild script that calls the SVCUtil utility to create the proxy everytime you build your project, but anyway ChannelFactory is much more neat and elegant.

Just wondering under what circumstances would you prefer to generate a proxy from a WCF service when you can just invoke calls using the ChannelFactory?

This way you won't have to generate a proxy and worry about regenerating a proxy when the server is updated?

Thanks

WCF ChannelFactory vs generating proxy

Visual Studio

服务器

我只是想知道在什么情况下，当您可以使用ChannelFactory调用调用时，您更喜欢从WCF服务生成代理？这样，您就不必生成代理并担心在服务器更新时重新生成代理了？谢谢

问WCF ChannelFactory与生成代理
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问WCF ChannelFactory与生成代理EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问WCF ChannelFactory与生成代理
EN