
Signature
Regards,
Debasish Pramanik
Assetlink India.
Phone: +91 20 26119531 (226)
> Why can't I access it as RequestHeader of the Service Object ?????
Sorry, I didn't notice that you were confusing the client and the server.
The service object does not exist on the client. What's on the client (in
your case) is a proxy class generated from the WSDL file which .NET produced
from the metadata on the server. .NET chose to create a proxy class with a
Header object called HeaderValue. That's not within your control.
So, don't worry about the name difference, as MyClass on the client and
MyClass on the server are two classes with almost no relationship between
them.
In other words, just use what works, HeaderValue, and don't expect the
client and server to be the same thing.
John
Debasish Pramanik - 19 Sep 2006 07:53 GMT
Hi John,
Thanks for the reply !!
I have seen some site whee they say it depend upon the namespace that you
can provide the attribute that controls the name. Do you have any idea about
that.

Signature
Regards,
Debasish Pramanik
Assetlink India.
Phone: +91 20 26119531 (226)
> > Why can't I access it as RequestHeader of the Service Object ?????
>
[quoted text clipped - 12 lines]
>
> John
John Saunders - 19 Sep 2006 10:52 GMT
> Hi John,
>
[quoted text clipped - 4 lines]
> about
> that.
No, sorry, I've never heard of anything like that. As far as I know, if you
use a Microsoft-generated proxy class, then you have to put up with
Microsoft-generated names.
John