I know only that basicHttpBinding supports having a .NET 2.0 client application.

Any other binding?

Not directly, although you can use WebHttpBinding to create a REST-style service with WCF, and use HttpWebRequest from the 2.0 client to call it. You can also use a custom binding which is equivalent to BasicHttpBinding, but that would be the same as using BasicHttpBindingin the first place.

Hi,

The answer is no, as in wcf the only binding has the backward compatibility is basicHttpBinding. This binding iscomsisted of TextMessageEncodingElement and HttpTransportBindingElement.

This binding will not support session state and transaction as these bindingElements are all supported by .net 3.0. For example in wsDualHttpBinding, the bindingElements are involved are:

element: System.ServiceModel.Channels.TransactionFlowBindingElement
element: System.ServiceModel.Channels.ReliableSessionBindingElement
element: System.ServiceModel.Channels.SymmetricSecurityBindingElement
element: System.ServiceModel.Channels.CompositeDuplexBindingElement
element: System.ServiceModel.Channels.OneWayBindingElement
element: System.ServiceModel.Channels.TextMessageEncodingBindingElement
element: System.ServiceModel.Channels.HttpTransportBindingElement

Thanks
Binze

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.

Not directly, although you can use WebHttpBinding to create a REST-style service with WCF, and use HttpWebRequest from the 2.0 client to call it. You can also use a custom binding which is equivalent to BasicHttpBinding, but that would be the same as using BasicHttpBindingin the first place.

Thank you Carlos.

Is it possible to create a custom binding that supports bidirectional and stateful communication? my client app is in .NET 2.0

Hi,

The answer is no, as in wcf the only binding has the backward compatibility is basicHttpBinding. This binding iscomsisted of TextMessageEncodingElement and HttpTransportBindingElement.

This binding will not support session state and transaction as these bindingElements are all supported by .net 3.0. For example in wsDualHttpBinding, the bindingElements are involved are:

element: System.ServiceModel.Channels.TransactionFlowBindingElement
element: System.ServiceModel.Channels.ReliableSessionBindingElement
element: System.ServiceModel.Channels.SymmetricSecurityBindingElement
element: System.ServiceModel.Channels.CompositeDuplexBindingElement
element: System.ServiceModel.Channels.OneWayBindingElement
element: System.ServiceModel.Channels.TextMessageEncodingBindingElement
element: System.ServiceModel.Channels.HttpTransportBindingElement

Thanks
Binze

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.