Web服务 - WCF与ASMX（＆QUOT;标准＆QUOT;） [英] Web Services -- WCF vs. ASMX ("Standard")

问题描述

我工作的一个新项目。是否有与一个WCF Web服务将在一个普通的旧时尚的Web服务的任何好处？

I am working on a new project. Is there any benefit with going with a WCF web service over a regular old fashion web service?

的Visual Studio提供了模板两者。有什么区别？优点和缺点是什么？

Visual Studio offers templates for both. What are the differences? Pros and cons?

推荐答案

什么是普通老式的Web服务？一个ASMX服务，或者您使用WSE呢？ ASMX服务不自然的互操作，不支持WS- *规范，并ASMX是老龄化速度非常快的技术。 WSE（Web服务增强功能）服务将增加对WS- *和可制成可互操作的，但WCF是为了取代WSE，所以你应该花时间去学习它。我要说的是，除非你的应用程序是一个快速的荤一过，你将获得巨大的灵活性，并最终有一个更好的设计，如果你选择的WCF。 WCF的确实的有一个学习曲线超出了[WebMethod]属性，但学习曲线过度夸大在我看来，它是指数比传统的ASMX服务功能更强大，面向未来。

What is a "regular old fashioned web service?" An ASMX service, or are you using WSE as well? ASMX services are not naturally interoperable, don't support WS-* specs, and ASMX is a technology that is aging very quickly. WSE (Web Service Enhancements) services DO add support for WS-* and can be made to be interoperable, but WCF is meant to replace WSE, so you should take the time to learn it. I would say that unless your application is a quick an dirty one-off, you will gain immense flexibility and end up with a better design if you choose WCF. WCF does have a learning curve beyond a [WebMethod] attribute, but the learning curve is over-exaggerated in my opinion, and it is exponentially more powerful and future proof than legacy ASMX services.

除非你的时间线根本无法忍受的学习曲线，你会做你自己一个大忙学习WCF，而不是仅仅使用ASP.NET Web服务的坚持。应用程序只会继续变得越来越分散和相互关联的，WCF是在微软平台上的分布式计算的未来。

Unless your time line simply cannot tolerate the learning curve, you would be doing yourself a huge favor learning WCF instead of just sticking with ASP.NET Web Services. Applications will only continue to become more and more distributed and interconnected, and WCF is the future of distributed computing on the Microsoft platform.

这里是两者之间的比较。

这篇关于Web服务 - WCF与ASMX（＆QUOT;标准＆QUOT;）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！