...
On Mar 29, 7:27 pm, "John Saunders" <john.saunders at trizetto.com>
wrote:
> <bjor...@gmail.com> wrote in message
>
[quoted text clipped - 23 lines]
> > My Question: Does somebody know how to fix those errors? Has it
> > something to do with Namespaces? I'm lost here.
> The two classes are not related in any way that matters to C#. Of course
> you're going to get errors. You'd get the same result if you passed an
> "int".
Ok, they are not related for C#. For me they are. Actually, for me
they are identical. So is there a way to typecast between the both? Or
do i have to create a copy constructor? Or is there another solution
to this problem?
Scott Holman - 30 Mar 2007 14:06 GMT
As john pointed out the classes are not the same. If your using WCF it is
fairly easy to modify the generated proxy code and replace class
implementations. If you are using pre .net3.0 web services you may be able
to do something similar.
You need to modify the generated client proxy class and replace the
generated LogService.Window class with House.Window. You need to make sure
that your implementation of House.Window is decorated with the same
attributes as the class in the generated client proxy. After applying the
same attributes you then need to modify the generated client proxy class to
use House.Window instead of LogService.Window.
Scott
John Saunders - 30 Mar 2007 20:43 GMT
> As john pointed out the classes are not the same. If your using WCF it is
> fairly easy to modify the generated proxy code and replace class
[quoted text clipped - 7 lines]
> same attributes you then need to modify the generated client proxy class
> to use House.Window instead of LogService.Window.
To my mind, it would be safer not to edit the proxy class, as it is a
generated class. Instead, yes, create a copy constructor.
John