我缺少有关WCF？ [英] What am I missing about WCF?

问题描述

我在质谱技术被开发的时间比我关心在这个阶段要记住。当.NET赶到现场时我以为他们一针见血的头部，并与每个迭代和版本我认为他们的技术都越来越强，并期待着每一个版本。

I've been developing in MS technologies for longer than I care to remember at this stage. When .NET arrived on the scene I thought they hit the nail on the head and with each iteration and version I thought their technologies were getting stronger and stronger and looked forward to each release.

不过，曾与WCF合作为去年我必须说，我发现这项技术非常困难的工作和了解。最初，它是相当有吸引力的，但是当你开始进入它的胆量，配置是一场噩梦，不必重写的邮件大小的行为，包含在消息的对象的数量，安全模型的复杂性，故障终于在废弃代理搬回来界定，而不是在XML中code接口。

However, having had to work with WCF for the last year I must say I found the technology very difficult to work with and understand. Initially it's quite appealing but when you start getting into the guts of it, configuration is a nightmare, having to override behaviours for message sizes, number of objects contained in a messages, the complexity of the security model, disposing of proxies when faulted and finally moving back to defining interfaces in code rather than in XML.

这是行不通的开箱即用，我认为它应该。我们发现所有的上述问题，而不是我们自己的测试，否则当我们的产品是出位。

It just does not work out of the box and I think it should. We found all of the above issues while either testing ourselves or else when our products were out on site.

我不明白这一切背后的基本原理，但他们肯定会想出更简单的实现机制。

I do understand the rationale behind it all, but surely they could have come up with simpler implementation mechanism.

我想什么我问的是，

• 难道我看着WCF走错了路？


• 它有什么优势比
  替代方案？


• 在什么情况下我应该
  选择使用WCF？

OK伙计们，很抱歉在应对延误，工作确实有碍事的坏习惯有时是：）

OK Folks, Sorry about the delay in responding, work does have a nasty habit of get in the way sometimes :)

一些澄清
我与WCF主漆点，我想掉进了以下几个方面
虽然它的工作开箱即用，你留下的引擎盖下的一些重大惊喜。正如上面基本的东西指出受到限制，直到它们被重写

Some clarifications My main paint point with WCF I suppose falls down into the following areas While it does work out of the box, your left with some major surprises under the hood. As pointed out above basic things are restricted until they are overridden

1. 串的大小比可以传递不能超过8K


2. 可以在一个单一的信息传递对象的数量受到限制


3. 代理不会自动从故障中恢复


4. 配置的量，同时它的存在是一件好事，但了解这一切，什么用什么，在哪些情况下可能很难理解。与不同的安全要求等部位部署软件尤其是当谈到配置，我们不得不隐藏很多我们的在后台数据库中，因为安全性和网络的人在现场试图更改配置文件中的事情不求甚解吧。


5. 保持在code接口的配置，而不​​是移动到XML明确定义的接口，可以通过几乎所有的东西公布和消费。我知道我们可以在XML从组装出口，但它充满垃圾和一些code发电机呛就可以了。

我知道世界上移动，我移动了过去（啊哈22年我一直在开发）多次和我积极利用WCF，所以不要误会我的意思，我不明白是什么它是在哪里它的标题。

I know the world moves on, I've moved on a number of times over the last (ahem 22 years I've been developing) and am actively using WCF, so don't get me wrong, I do understand what it's for and where it's heading.

我只是觉得应该有提供简单的配置/部署选项，轻松设置和更好的管理配置（SQL配置提供商也许，而不只是在web.config /的app.config文件）。

I just think there should be simpler configuration/deployment options available, easier set-up and better management for configuration (SQL config provider maybe, rather than just the web.config/app.config files).

推荐答案

我使用WCF现在所有的时间和我分享你的痛苦。现在看来似乎是严重过度设计，但是我们要与它坚持了很长一段时间，所以我努力学习吧。

I use WCF all the time now and I share your pain. It seems like it was grossly over-engineered, but we are going to be stuck with it for a long, long time so I'm trying to learn it.

有一件事我肯定有关，XML很烂。我有什么，但使用XML来控制它，并已改经处理code一切问题。

One thing I am certain about, XML sucks. I've had nothing but problems using XML to control it and have since switched to handling everything via code.

这篇关于我缺少有关WCF？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！