.net - Webサービスの自家消費

original title: ".net - Homegrown consumption of web services"


Translate

I've been writing a few web services for a .net app, now I'm ready to consume them. I've seen numerous examples where there is homegrown code for consuming the service as opposed to using the auto generated methods that Visual Studio creates when adding the web reference.

Is there some advantages to this?



.netアプリ用にいくつかのWebサービスを作成してきましたが、今はそれらを使用する準備ができています。自動を使用するのではなく、サービスを利用するための独自のコードがある多くの例を見てきました...

これは翻訳後の要約です。完全な翻訳を表示する必要がある場合は、「翻訳」アイコンをクリックしてください。


すべての答え
  • Translate

    No, what you're doing is fine. Don't let those people confuse you.

    If you've written the web services with .net then the reference proxies generated by .net are going to be quite suitable. The situation you describe (where you are both producer and consumer) is the ideal situation.

    If you need to connect to a web services that is unknown at compile time, then you would want a more dynamic approach, where you deduce the 'shape' of the web service.

    But start by using the auto generated proxy class, and don't worry about it until you hit a limitation. And when you do -- come back to stack overflow ;-)