asmx文件_将Web服务的实现与ASMX文件分开

asmx文件

A fellow said recently that he wanted to build a "monster web service" with over 20 classes and over 20 methods (well, not THAT monster, but not Hello World). He said:

一位同僚最近说，他想构建一个具有20多个类和20多种方法的“怪物Web服务”(嗯，不是那个怪物，而是Hello World)。 他说：

Is there any way to provide my consumers with a single end-point (.asmx) exposing these methods from several different class files? I can't see my dev team all working on a single ASMX file...what am I missing here?

有什么方法可以为我的使用者提供一个单一端点(.asmx)，以从多个不同的类文件中公开这些方法？ 我看不到我的开发团队都在处理单个ASMX文件...在这里我缺少什么？

It's easy to make the assumption that the ASMX file has some magic and that everything needs to go in it. But the ASMX is just an endpoint like an ASPX or ASMX. It gives IIS and ASP.NET something to think about, but it's just a broker - even less - it's a front.

可以很容易地假设ASMX文件具有魔力，并且所有内容都需要放入其中。 但是ASMX只是一个端点，例如ASPX或ASMX。 它为IIS和ASP.NET提供了一些考虑因素，但它只是一个代理，甚至更少，它是一个前台。

DasBlog has a Web Services interface, thanks to Clemens and the crew before Omar and I, and here's the contents of it's EditService.asmx.cs:

DasBlog具有Web服务接口，这要感谢Clemens和Omar和I之前的工作人员，这是EditService.asmx.cs的内容：

[WebService(Namespace&#