-
Thanks for responding!
-
Hello, I have a Silverlight CSLA project in VS2010 and it had been working with 4.3+ just fine. Then I upgraded to 4.5.10 when that was released using Nuget. Unknown at the time, the BeginSave method would fail to call the Saved event if an exception was thrown in the DataPortal_Update method. I didn't test any other scenarios. It used to be called
-
I agree that the DataPortal_Create method with no parameters should be left as is. My concern is when I'm making a data portal call with a criteria. I was under the impression that if a DataPortal_Xxx method with a matching signature was not found then the call would fail ,or go to the server if remoting was set up, and try again there. So I was
-
As time goes on we will all be moving towards the new capabilities, so functional parity is a good thing. I wouldn't want to spin up threads just because. Is the creating of unnecessary threads the 'async behaviors' you're concerned with?
-
Hi Rocky, For the most part, I agree that it's a feature, not a bug. However, in the case where I have a non-parameterless DP_Create method that only exists in the server-side code (excluded from client-side by preprocessor), Csla, of course, doesn't find the method matching the signature. It then seems to proceed to run the default parameterless
-
I have the same problem in Silverlight. It turns out you don't need to create a DataPortal_Create(Criteria type) matching your server-side dataportal call. For me it works as long as I just override the default DataPortal_Create() method to remove the [RunLocal] attribute, even if my DataPortal_Create method has parameters. It indeed seems like
-
I use MVVM when editing a child object from a list. My view model follows the same patterns as Rocky has suggested inheriting the Csla.Xaml.ViewModel class. I pass in both the child object and the root object into the constructor. Within the view model constructor I do a BeginEdit on the root and set the VM model to the child object. I then override
-
Sorry for not including the versions of everything. I'm using CSLA 4.3.10 and Silverlight 5.
-
Hello, After further investigation, I found where the problem lies. By changing the following code in the FieldDataManager.OnSetState if (value.Value != null && mode == StateMode .Undo && typeof ( IMobileObject ).IsAssignableFrom( property.Type ) && ! typeof ( IUndoableObject ).IsAssignableFrom( property.Type )) { data.Value
-
Hello, In Silverlight, this minor bug will still creep in if the property type is a Nullable IMobileObject. For instance having a nullable SmartDate will cause the undo to fail if this property is not set to null. It is easy to replicate. I created this Root class: [ Serializable ] public class Root : BusinessBase < Root > { public static readonly