-
I am attempting to rework the AccountController in the MVC4 default template so it uses CSLA rather than SimpleMembership because SimpleMembership didn't meet my requirements. I am replacing the command-based architecture with CSLA business objects. Right now I am working with the UserRegister business...
-
Oh, I see - your question was about the Command object not inheriting from CommandBase? The answer to that is a little more complex. In pure .NET code the data portal will do what you describe, because it only cares that the type is Serializable and that you implement the appropriate DataPortal_XYZ methods...
-
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...
-
The data portal requires that all types you pass through the data portal implement IMobileObject. The easiest way to accomplish this is to subclass one of the CSLA base types. In your case, subclass CriteriaBase. Also, make sure to use managed backing fields so they automatically serialize. Otherwise...
-
To make it short, the MobileFormatter must already know how to serialize types (which it does for basic types, but List<T> is not one of them). Otherwise, the object must "participate" in the serialization process, as Rocky said in some posts. For the object to participate, you must override...
-
Hi, we are using CSLA v3.8.1.0 in a WPF application. The application is working fine when connecting to a local dataportal (with Slovak regional settings), but when connecting to a dataportal hosted on our dev server (with English regional settings) the properties of the business objects are getting...
-
You may want to read the Using CSLA 4 books - at least the data portal book that covers serialization in some detail. CSLA uses its own serializer for Silverlight, called the MobileFormatter. To avoid the use of reflection (because reflection is too restricted on Silverlight to be useful for serialization...
-
This wouldn't be the first time Microsoft has changed the serialization format out from under us. But it would be the first time they were incompatible since the .NET 1.0 to 1.1 fiasco. I suggest you do two things: Submit a bug to Microsoft via connect, so they know they are potentially repeating...
-
The two immediate possibilities that come to mind: Your object graph is massive, and serializing it literally does cause the DataContractSerializer to hit some memory limit Your object graph has a circular reference, and serializing it causes an infinite loop of serialization that results in consumption...
-
Hello nice people out there :) I've run into very interesting problem. So far I am using CSLA 4.1 and have built WCF Service (the standart CSLA built-in service) so I can use CommandBase to execute code on the server (n-tier appliation). Most of the CommandBase objects are working fine. The interesting...