Changes to DataPortal proxies for CSLA 4.5 - E.g. what diff between MobileProxy and WcfProxy

Changes to DataPortal proxies for CSLA 4.5 - E.g. what diff between MobileProxy and WcfProxy

Old forum URL:

Jaans posted on Sunday, November 04, 2012

I'm looking at creating a custom client site data portal proxy, and in doing so noticed the proxy classes for CSLA 4.5 had changed quite a bit.

It looks like EnterpriseServices proxy and Remoting proxy have been removed and Mobile proxy has been added.

Is there some information available about the new Mobile proxy? When should we use it (if at all) and how is it different from the WcfProxy?

JonnyBee replied on Tuesday, November 06, 2012

The MobileProxy uses the MobileFormatter and pre 4.5 was only available for Silverlight/WP which is now also available for .NET applications. 

IE: You can have a more common codebase and N-tier server for SL, .NET and WP.
Previously you would have one proxy endpoint for SL/WP and another endpoint for .NET.

The MobileProxy uses another contract envelope (and server side proxy) and has a better Exception message to provide error message to client (and will not serialize the actual Exception).

In all essence the MobileProxy is a NET implementation of the pre 4.5 Silverlight class Csla.DataPortalClient.WcfProxy

Jaans replied on Tuesday, November 06, 2012

Ah.. ok. Thank you for that.

Would it be safe to make the statement that MobileProxy the preferred default formatter for CSLA 4.5 when using SL/WP/RT?.

RockfordLhotka replied on Wednesday, November 07, 2012

Not just the default, but the only option unless you want to write your own. The Microsoft serializers (BinaryFormatter and NDCS) don't exist on those platforms so they aren't an option.


What we've done is made MobileFormatter an option on .NET where it wasn't before. This should support partial trust scenarios like on a multi-tenant web server.

Copyright (c) Marimer LLC