Getting unable to cast error (when same object is referenced in client and web service)

[Rahul]

I am getting following error:

1) For a xml file "Request.xm l" we created a schema "Request.xs d".

2) With the help of xsd.exe we got the C# file Request.cs.

3) We tried to send the object of Request.cs to a webservice method
SaveRequest(Req uest req).

4) Scenario is like same Request.cs is referenced by both server and
client.

5)When we are trying to pass the req object of type Request we are getting
unable to cast error.

Is this expected? If so, are there any workarounds?
Please help us in solving this.

Thanks !!!!!

[John Saunders [MVP]]

"Rahul" <ra****@rediff. comwrote in message
news:ui******** ******@TK2MSFTN GP02.phx.gbl...

>I am getting following error:

1) For a xml file "Request.xm l" we created a schema "Request.xs d".

2) With the help of xsd.exe we got the C# file Request.cs.

3) We tried to send the object of Request.cs to a webservice method
SaveRequest(Req uest req).

4) Scenario is like same Request.cs is referenced by both server and
client.

5)When we are trying to pass the req object of type Request we are getting
unable to cast error.

Is this expected? If so, are there any workarounds?

This is expected. The classes on the client side are proxy classes only -
they are not meant to be the same as the server-side classes. Their only
purpose is to make it easier for you to call the web methods exposed by the
server.

In fact, if you ever get a situation with ASMX web services where you have
the same class on the client and the server, then you've almost certainly
made a very serious mistake.
--
--------------------------------------------------------------------------------
John Saunders | MVP - Windows Server System - Connected System Developer