What's the advantage of a WCF client if I can use a Webservices 2.0 client just as fine?
Recently a couple of WCF services have been introduced to our company's API.
There are sample implementations for Windows that make use of proxy codes generated by Visual Studio 2010 (either full WCF client or Silverlight code). All looking nice.

Then I figured out that it is also possible to let Studio generate a Webservices 2.0 client code proxy and what can I say:

 * It works just as fine as the WCF client
 * It also returns real objects, just like WCF
 * It is also using SOAP

What the heck is the difference/advantage of a native WCF client?

Please note that I'm especially interested in the CLIENT SIDE. The server side is a different story. 
What's the advantage of a WCF client if I can use a Webservices 2.0 client just as fine?
===

Recently a couple of WCF services have been introduced to our company's API.
There are sample implementations for Windows that make use of proxy codes generated by Visual Studio 2010 (either full WCF client or Silverlight code). All looking nice.

Then I figured out that it is also possible to let Studio generate a Webservices 2.0 client code proxy and what can I say:

 * It works just as fine as the WCF client
 * It also returns real objects, just like WCF
 * It is also using SOAP

What the heck is the difference/advantage of a native WCF client?

Please note that I'm especially interested in the CLIENT SIDE. The server side is a different story. 