Matevž Gačnik's Weblog

The following is a list of Windows Communication Foundation (read Indigo) changes from September CTP (beta 1) to November CTP (beta 2 RC0).

Most of them are name changes. Nevertheless, you will need to update at least configuration, since element/attribute naming there has changed quite a lot.

Class name changes:

1. Fault<T>       FaultException<T>
2. UnknownFault   UnknownFaultException
3. ServiceSite    InstanceContext

Parameters of [OperationBehaviour] attribute:

1. AutoCompleteTransaction TransactionAutoComplete
2. AutoEnlistTransaction   TransactionScopeRequired

Other changes:

1. ServiceHost<T>   ServiceHost(typeof(T)>

Binding names:

1. wsProfileBinding            wsHttpBinding
2. netProfileTcpBinding        netTcpBinding
3. netProfileDualTcpBinding    netTcpBinding
4. netProfileNamedPipeBinding  netNamedPipeBinding
5. basicProfileBinding         basicHttpBinding

Configuration element/attribute name changes:

1. /services/service[@serviceType]                   /services/service[@type]
2. /endpoints/endpoint[@contractType]                /endpoints/endpoint[@contact]
3. /services/service/endpoint[@bindingSectionName]   /services/service/endpoint[@binding]
4. /behaviors/behavior[@configurationName]           /behaviors/behavior[@name]
5. /bindings/*/binding[@configurationName]           /bindings/*/binding[@name]

Attribute changes:

1. [BindingRequirements(TransactionFlowRequirements=RequirementsMode.Require)]
   [TransactionFlow(TransactionFlowOption.Required)] 
2. [BindingRequirements(QueuedDeliveryRequirements=RequirementsMode.Require)
   [BindingRequirements(QueuedDeliveryRequirements=BindingRequirementsMode.Required)
3. [InstanceMode=InstanceMode.Singleton]
   [InstanceContextMode=InstanceContextMode.Single]
4. [InstanceMode=InstanceMode.PrivateSession]
   [InstanceContextMode=InstanceContextMode.PerSession]
5. [InstanceMode=InstanceMode.PerCall]
   [InstanceContextMode=InstanceContextMode.PerCall]
6. [InstanceMode=InstanceMode.SharedSession]
   [InstanceContextMode=InstanceContextMode.Shared]

This list may not be complete.

I do expect that QueuedDeliveryRequirements property of [BindingRequirements] attribute will be standalone when Indigo ships. There's no point in having a separate attribute for expected transaction semantics and leave out the queued delivery. It's the same concept being pushed down to administrators (binding requirements are fixed requirements which are supposed to be met by the admin - they are the developers' law of expected processing model).

Maybe this attribute should be named [QueuedDelivery], with appropriate property for demanding it (like QueuedDeliveryOption) and a property called OrderedSessionOption, which would handle ordered session maintenance.