Repost: WCF CallbackContract with inherited interfaces -> bad prox

[=?Utf-8?B?Sm9zw6kgSm95ZQ==?=]

---------------------
This question has already been posted. I got a tip to use
[NetDataContractSerializer] and also get rid of svcutil.exe. However, I
still want to understand why it does not work the "official" way.
previous post:
http://groups.google.com/group/micro...123e0375500a9b

I tried to post it another time. But it seems not to appear in newsgroup
(seems to be related to my attachement???)
---------------------

I'm protyping an application with WCF and I'm trying to define a Callback
Contract with an interface that derives from another one.
Doing so, the generated proxy code (using svcutil.exe) does not see the base
interface and a "NotSupportedException" is thrown on the Server when trying
to call methods defined in base interface.
I have also tried to manually define the base interface in the proxy class
so as to be able to implement the methods in the client -Same behavior.

Does anyone knows why it does not work?

Thanks for any help and sorry for the repost!
José
Here is my contract definition :

namespace wcfContract
{

[ServiceContract(Namespace = "Test")]
public interface IPing
{
[OperationContract]
void Ping();
}

public interface ITestCallback : IPing <-------------- IPing method
not seen at all in proxy
{
[OperationContract]
void TestCB();
}

[ServiceContract(Namespace = "Test", CallbackContract =
typeof(ITestCallback))]
public interface ITest : IPing
{
[OperationContract]
void Test();
}
}

[sloan]

Jose,

I notice you keep coming up empty on this request.

Try
http://forums.microsoft.com/msdn/sho...d=118&siteid=1

or
microsoft.public.windows.developer.winfx.indigo

I think the forum is your best bet.

That's such a specific wcf question...that the forums is probably your best
shot.

Then let me know me what you find! (by posting back here I guess).
I'm curious as well, just not as curious as you are. (Well, not enough time
to check it).

Good luck.



"José Joye" <Jo*****@discussions.microsoft.comwrote in message
news:7D**********************************@microsof t.com...

---------------------
This question has already been posted. I got a tip to use
[NetDataContractSerializer] and also get rid of svcutil.exe. However, I
still want to understand why it does not work the "official" way.
previous post:
http://groups.google.com/group/micro...123e0375500a9b

I tried to post it another time. But it seems not to appear in newsgroup
(seems to be related to my attachement???)
---------------------

I'm protyping an application with WCF and I'm trying to define a Callback
Contract with an interface that derives from another one.
Doing so, the generated proxy code (using svcutil.exe) does not see the
base
interface and a "NotSupportedException" is thrown on the Server when
trying
to call methods defined in base interface.
I have also tried to manually define the base interface in the proxy class
so as to be able to implement the methods in the client -Same behavior.

Does anyone knows why it does not work?

Thanks for any help and sorry for the repost!
José
Here is my contract definition :

namespace wcfContract
{

[ServiceContract(Namespace = "Test")]
public interface IPing
{
[OperationContract]
void Ping();
}

public interface ITestCallback : IPing <-------------- IPing method
not seen at all in proxy
{
[OperationContract]
void TestCB();
}

[ServiceContract(Namespace = "Test", CallbackContract =
typeof(ITestCallback))]
public interface ITest : IPing
{
[OperationContract]
void Test();
}
}