proxy generated by WCF differs from proxy generated by Web Service

[sat]

I am trying to convert an existing web service to WCF. But i could see that
the WCF generated proxy differs from old proxy of Web Service. For example if
exists a property by name "items" in old proxy (Web Service generated), then
in new proxy of WCF, it is coming as "_items".

Is WCF created proxy compatible with old proxy of Web Service ?
What do I need to do to make it work?

[Maxwell]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

By nature of a proxy to a Web service, as long as the proxy is generated
correctly (more on that in a bit), it should work if the Web service
itself doesn't change. Likely you are creating these proxies from a
live, reachable Web service, or from a WSDL file output by such a
service. The WSDL file is the contract which says "this is how the Web
service will be communicating, and expecting the clients to communicate
to it". It is a language-neutral piece of meta-data which lets Web
service proxies be written for multiple languages.

I could write or generate a proxy for the same service in ECMAscript,
C#, Perl, or Python, and they will all "look different" with respect to
the written or generated code. But as long as the coding is sound
(written or generated), and conforms to the contract specified by the
WSDL file, it will communicate with the Web service properly.

Web service proxies are a way to communicate with Web services,
abstracting the implementation of the network application protocol
(HTTP, using POST, GET, SOAP, etc) into a language-specific
representation of methods and classes. This is so that when a Web
service is "used" in your application, you're not setting up the HTTP
parameters and WebServiceRequest object each time, for example. You can
think relatively safely in terms of function calls and return values.

So likely, the proxy generation process did change the resulting code,
for style, API, or performance reasons, but ultimately, both proxies
should be compatible to the same Web service. Have there been any
changes to accessibility in the source code generated? You may need to
alter the source generated, or update the rest of your source code to
use these new generated classes. Or, use the old generator, and in your
new code, call using the old style. I'm not intimately familiar with the
inner workings of wsdl.exe, but at the end of the day, if it talks the
same WSDL, you're probably good to go.

- -- Maxwell
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32) - WinPT 1.2.0

iQEcBAEBAgAGBQJKOkmKAAoJEB/xjSmapNjLNFYIALh0W9u5l0LtI99h5G3NH9R+
C7EszidaZSXuiJaDxSimDywkNl9D5ZQ23UMu6BXIF24ozMmfF9QlPBOd/knpiQ0x
maqBN3fgPl8OLxUt/fJUQSq6u/aaOrSE8nTOtx+zoZtJp8hpvm6wN05xlGTH3bNu
fzJ8WuHViumHW1vagPfuBuLku6LIj687mMztlpRIYaRUaVxlSG3qHhKnhrtg+Tt6
LRM6XqIzYC49ho1Vfxi20I5wJUARiBrJB1lX0UuoMTeCAtmTyn31OZc7EpOT0U+d
anI65GxHtvTANrLRfEpEwZt6f78wozqPbhqUx/gtK3gvkYfjJbI/Xwxacitkuds=
=UpaK
-----END PGP SIGNATURE-----