What is the model for integrating the CSLA with .NET 3.0Windows Communication Foundation?
I am working closely with the Connected Systems group in Redmond on this, and related technologies. Additionally, when I build CSLA .NET 2.0 I specifically designed it to allow for near-seamless integration of WCF. Right now you can get an early version of a data portal channel for WCF http://www.lhotka.net/Article.aspx?area=11&id=0eec56bb-2a61-47c4-a9ca-f98371db1cad This allows existing applications using Remoting, Web Services or Enterprise Services to transition to WCF with NO CODE CHANGES. This is a very compelling feature of CSLA in my view. Unfortunately that’s not the whole story, and that’s why a new version of CSLA will be required in the .NET 3.0 timeframe. CSLA uses the BinaryFormatter for some scenarios (n-level undo, cloning). To support the DataContract model, the NetDataContractSerializer is required instead, so the formatter needs to be pluggable. Again, I’ve been working with the PM who owns serialization, and this is not a major change to CSLA, and other than there be
