Sharing web-service class between two local assemblies

[Josh]

I have application1 that connects to webService1. I have a second
application that references the same webservice (webService1). I need
to pass an instance of a class returned from webService1 from
application1 to application2. I have a reference (assembly.load) of
application2 in application1, but when it won't let me cast it -
saying they're different types. What are my options?

Thanks in advance,
Joshua Moore

[John Saunders]

"Josh" <gl*****@gmail.comwrote in message
news:11**********************@p10g2000cwp.googlegr oups.com...

>I have application1 that connects to webService1. I have a second
application that references the same webservice (webService1). I need
to pass an instance of a class returned from webService1 from
application1 to application2. I have a reference (assembly.load) of
application2 in application1, but when it won't let me cast it -
saying they're different types. What are my options?

They are different types. They are unrelated to each other. That's how it's
supposed to be.

webService1 did not return an instance of a class. It returned some XML
which was later deserialized into a class instance.

John

[Joseph Geretz]

Try this.

Create a library which contains your class definition. The class must be
serializable. All three projects should reference this library. The Web
Service should send back an instance of your class definition. This class
should then be transportable between application1 and application2. This
should work, since all three applications are using the same definition of
the class.

Haven't had time to test this out specifically, but I think this should
work. Let me know if I'm wrong about this.

Hope this helps.

- Joseph Geretz -

"Josh" <gl*****@gmail.comwrote in message
news:11**********************@p10g2000cwp.googlegr oups.com...

>I have application1 that connects to webService1. I have a second
application that references the same webservice (webService1). I need
to pass an instance of a class returned from webService1 from
application1 to application2. I have a reference (assembly.load) of
application2 in application1, but when it won't let me cast it -
saying they're different types. What are my options?

Thanks in advance,
Joshua Moore

[John Saunders]

"Joseph Geretz" <jg*****@nospam.comwrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl...

Try this.

Create a library which contains your class definition. The class must be
serializable. All three projects should reference this library. The Web
Service should send back an instance of your class definition. This class
should then be transportable between application1 and application2. This
should work, since all three applications are using the same definition of
the class.

Haven't had time to test this out specifically, but I think this should
work. Let me know if I'm wrong about this.

Joseph, this doesn't work at all.

The Web Services platform erects a "chinese wall" between the client and the
server. The client is NOT using the classes exposed by the server. A .NET
client will be using proxy classes created by .NET. These proxy classes will
be unrelated to the original classes exposed by the server.

This becomes obvious when the exposed classes contain methods which are not
[WebMethod]s. Those methods are not part of the interface that the client
sees, even if they are public. Neither will the client see any constructors
other than a default constructor, nor will it see indexers, events, etc.
These things are not part of the Web Services Platform.

John

[John Saunders]

"Joseph Geretz" <jg*****@nospam.comwrote in message
news:O1*************@TK2MSFTNGP06.phx.gbl...

>Joseph, this doesn't work at all.

Actually John, it does work with just a little bit of additional effort.
The attached project demonstrates the technique.

>The Web Services platform erects a "chinese wall" between the client and
the
server. The client is NOT using the classes exposed by the server. A .NET
client will be using proxy classes created by .NET. These proxy classes
will
be unrelated to the original classes exposed by the server.

As I'll say for the third and final time, this doesn't work. Your edits will
be destroyed as soon as Update Web Reference is performed.

I'm going to shut up now, and let somebody else make these points for me (I
hope). We seem to have gotten to the point where you're ignoring what I say
because it's me saying it.
John

[Joseph Geretz]

As I'll say for the third and final time, this doesn't work. Your edits

will be destroyed as soon as Update Web Reference is performed.

Duh. But if you're willing to put the same edits in place (come on John,
you're the guy who dislikes all this 'magically generated' wire-up
infrastructure to begin with - the 'training wheels' as you so eloquently
describe it) this can be a workable solution. Especially, once you get your
Web Service interface locked down, and are no longer updating Web References
with any degree of frequency.

I'm going to shut up now, and let somebody else make these points for me
(I hope). We seem to have gotten to the point where you're ignoring what I
say because it's me saying it.

The bottom line is, if you're willing to put some edits in place, this can
be a workable solution. Especially, once you get your Web Service interface
locked down, and are no longer updating Web References with any degree of
frequency. Obviously, there's a choice to make here. If you want to go with
the training wheels (your terminology) without getting involved in the proxy
yourself, then this is a non-starter. But if you're ready to tak the
training wheels off and get invoved in the code yourself, then this can be a
workable solution.

Your fundamental resistance to this approach doesn't seem quite consistent
with your previously stated distaste for 'magically generated' wired-up
infrastructure - the 'training wheels' as you've referred to this in the
past. Given this basic inconsistency in your own position, one might be
forgiven for oppining that perhaps the exact opposite is true. That we've
gotten to the point where you are ignoring the basic facts, simply because
it's me who is presenting them. But I see that your mind is made up; I'll
stop confusing you with the facts now, so that you can continue to cling to
your assertions.

- Joseph Geretz -

"John Saunders" <john.saunders at trizetto.comwrote in message
news:eF**************@TK2MSFTNGP06.phx.gbl...

"Joseph Geretz" <jg*****@nospam.comwrote in message
news:O1*************@TK2MSFTNGP06.phx.gbl...

>>Joseph, this doesn't work at all.

Actually John, it does work with just a little bit of additional effort.
The attached project demonstrates the technique.

>>The Web Services platform erects a "chinese wall" between the client and
the
server. The client is NOT using the classes exposed by the server. A
.NET
client will be using proxy classes created by .NET. These proxy classes
will
be unrelated to the original classes exposed by the server.

As I'll say for the third and final time, this doesn't work. Your edits
will be destroyed as soon as Update Web Reference is performed.

I'm going to shut up now, and let somebody else make these points for me
(I hope). We seem to have gotten to the point where you're ignoring what I
say because it's me saying it.
John