我一直在与web服务了2年多了。我有很多要说的服务，如SOAP 1.2，WSDL的方式进行通信时，和其他的东西100。

I have been working with webservices for over 2 years now. I have lot to say about services like Soap 1.2, WSDL, the way communication is taking place and 100 of other things.

我看到有人在谈论他们的重型ASMX背景和Web服务的expertize。但是，当涉及到实现我不觉得什么，但添加Web引用，并调用从C＃几个方法。所有这一切我们谈论（序列化，反序列化，肥皂，等等等等）的事情是照顾微软内部。

I have seen people talking about their heavy ASMX background and web services expertize. But, when it comes to implementation I don't find anything but adding a web reference and calling few methods from C#. All the things that we talk about (serialization, deserialization, soap, blah blah) is taken care by Microsoft internally.

所以，我想知道这是否是我们所必须做的，同时对付Web服务或者是有什么更给它？

So I want to know if it is all we have to do while dealing with WebServices or is there anything more to it?

另一种方式：我瓦纳知道什么ASMX的专家必须了解这些服务

Rephrase: I wana know what an expert of ASMX must know about these services.

我会AP preciate，如果你能提供一些很好的参考，材料或任何评论这一点。

I'll appreciate if you can provide some good references, material or any comments on this.

推荐答案

我觉得你是从实现者/工具的角度处理这一点;是的，Visual Studio中做了很多繁重的工作，使开发人员觉得调用Web服务是一样的调用任何方法 - 但谁使用的工具盲目不知道开发商什么$正在生成C $ c和这一切是如何作品，正如你提到的，不是专家。

I think you are approaching this from a implementor/tools standpoint; yes, Visual Studio does a lot of the heavy lifting to make a developer feel like calling Web services is the same as calling any method -- but developers who use the tools blindly without knowing what code is being generated and how it all works are, as you suggest, not experts.

如果说你是一个专家，我认为你必须能够谈论的事情类似如下：

To say you are an expert, I think you would need to be able to talk about things like the following:

赞成并在你的架构使用服务的缺点（性能方面的考虑，版本问题，同步与异步，等等。） 的原因，你可能需要使用ASMX与WCF 在SOAP协议，SOAP头如何被用于保障等内部implementaiton。 知识的内部，所以你可能会暴露业务由非微软的客户消费（java的，等等。） 在华尔街英语的特点，包括不同的版本 在安全问题 - 如何确保对服务的访问，以及如何保护正在传输的数据来回