http://msmvps.com/blogs/williamryan/archive/2008/11/01/wf-persistence-where-datacontract-serializable.aspxLet&#39;s say you were using Workflow Foundation (WF) and Windows Communication Foundation (WCF). Assume you wanted to use WF&#39;s Persistence mechanism (which requires types to be Serializable ). And assume that all the objects you were using in theenCommunityServer 2008.5 SP2 (Build: 40407.4157)http://msmvps.com/blogs/williamryan/archive/2008/11/01/wf-persistence-where-datacontract-serializable.aspx#1655075Wed, 26 Nov 2008 00:10:26 GMTd67277c4-116b-43f1-b688-e9ef184ea916:1655075Russell<p>This article was given to me by a coworker, as he had to hear my venting due to this issue. &nbsp;Thanks, it describes the WCF/WF data divide well.</p> <p>The kicker, for me, is that the ExtensionDataObject used for round-tripping in WCF is neither [Serializable], nor inheritable. &nbsp;So all the easy ways I could&#39;ve made my WCF data contracts play nice with everybody are cut off. &nbsp;Any suggestions?</p> <div style="clear:both;"></div><img src="http://msmvps.com/aggbug.aspx?PostID=1655075" width="1" height="1">http://msmvps.com/blogs/williamryan/archive/2008/11/01/wf-persistence-where-datacontract-serializable.aspx#1652848Sun, 02 Nov 2008 22:03:30 GMTd67277c4-116b-43f1-b688-e9ef184ea916:1652848Kelly Martens<p>Excellent subject and thinking on this Bill. Though it is in fact in its infancy I do think we will see widepsread adoption over the next few years.</p> <div style="clear:both;"></div><img src="http://msmvps.com/aggbug.aspx?PostID=1652848" width="1" height="1">