DavideZordan.net

I’ve already blogged about the new Silverlight 3 Beta Duplex support here. In these days I’ve found some interesting articles and tips about this topic, so this is a list of links I’ve found useful:

• Improve PollingDuplex reliability with Silverlight 3.0 by Andrea Boschin
• Silverlight Tip: Problems with polling duplex inactivitytimeout. by Alexey Zakharov
• How to increase amount of silverlight duplex clients. by Alexey Zakharov
• Silverlight Tip: If Polling Duplex SLOWS Everything =) by Alexey Zakharov
• What’s new with web services in Silverlight 3 Beta by the Silverlight Web Services Team
• How to: Build a Duplex Service for a Silverlight Client
• How to: Access a Duplex Service

I’m testing the updated Duplex support available in Silverlight 3 Beta, the important news is the possibility to simplify and reduce the code in the client:

• now it’s possible to use the “Add Service Reference” functionality of Visual Studio to consume the service;
• in this way you the use of channels can be avoided by simply attaching a callback to an event.

I’ve prepared an example based on the material available on the official documentation, download the complete solution from here.

Great news:

• Binary message encoding;
• Duplex object model simplification;
• Faults support;
• New security mode;
• Command-line proxy generation.

Check out the original post by the Silverlight Web Services Team.

Remember also to download the samples available here.

Check out this excellent post by Tim Greenfield.

What is WS-Discovery? As described in this excellent post by Jesus Rodriguez, WS-Discovery is an OASIS Standard that defines a lightweight discovery mechanism for discovering services based on multicast messages. Read the post for an example of its use in WCF 4.0.

Suriel  Bendahan has written a great article about this topic on CodeProject, source code available!

As reported by the Web Services Team, Silverlight 2 supports custom SOAP headers. 

A good working example can be found here, but it only uses WCF services, what about the “old” asmx ones?

I’ve modified the “SilverlightHeaders” solution to use both WCF and asmx, using OperationContext in the first case and HttpContext in the last, click here to download the complete solution.

Check out this great article by David Betz.

Click here to download some useful examples, including a Duplex-service example and an implementation of SOAP faults and custom SOAP headers.

One of the new features of .NET framework 3.5 SP1 is the possibility to serialize an object graph with circular references by using the standard xsd:ID/xsd:IDREF attributes.

Just mark your DataContract attribute with the IsReference=true property:

    [DataContract(IsReference=true)]

    public class Room

    {

        [DataMember]

        public string description { get; set; }

        [DataMember]

        public Devices roomDevices { get; set; }

    }

 Check out this post by Zulfiqar for more examples.