I've been trying to debug a TP -> RTM issue and I've gotten to the point
where I'm reviewing every line of code. One of these lines is particularly
strange -- it shouldn't compile, but does.
I'm calling the SoapReceivers.Add(Uri, SoapService) overload, which doesn't
exist. The docs state, and Reflector confirms (I hope), that the only
overloads for this method follow:
public static void Add(EndpointReference, SoapReceiver);
public static void Add(EndpointReference, Type);
public static void Add(EndpointReference, SoapReceiver, bool);
public static void Add(EndpointReference, Type, bool);
(Note the first parameter.)
SoapReceiver's base type is Object, so I'm not calling a superclass's
method, and the only similarity in Uri and EndpointReference's type
hierarchies is that Object is the root type.
What have I missed? This isn't related to the problem I'm trying to solve;
I'm really looking for someone to embarrass me and point out something
painfully obvious.
Thanks!
-jk
Curt Hagenlocher - 24 Jun 2004 19:58 GMT
> I'm calling the SoapReceivers.Add(Uri, SoapService) overload, which doesn't
> exist. The docs state, and Reflector confirms (I hope), that the only
[quoted text clipped - 8 lines]
>
> What have I missed?
You can construct an EndpointReference from a Uri.
--
Curt Hagenlocher
curth@motek.com
Jeff Key - 24 Jun 2004 20:11 GMT
Found it: Implicit type conversion from Uri -> EndpointReference.
-jk
> I've been trying to debug a TP -> RTM issue and I've gotten to the point
> where I'm reviewing every line of code. One of these lines is particularly
[quoted text clipped - 21 lines]
> Thanks!
> -jk