-
I saw some 2010 posts on this topic, but they seemed dated. So I will ask what is likely been beaten down before. We are using .NET, CodeSmith generation, MEF, Prism, WPF and MVVM technologies/patterns. The short version is: How can I initialize a child object on creation? Explanation: I have a "Flight" record (Editable Root). This Flight
-
AH HAH! I was in the wrong book
-
Well, that goes back to my original post then. It indicated that I was using an Editable Root List with Editable Child objects and the save fails because I "cant save a child object directly". I am calling save on my Editable Root List which itterates over the child objects and calls save on them. Another poster indicated that I was mixing
-
Thanks Rocky, The UI guys are handling the freshness of the loaded objects and that sort of thing. I am only baffled by which meta-types (Editable Root List/Editable Root, Dynamic Root List/Dynamic Root, etc) that I should use to support the UI developers. I just need a list/object pair that I can load and save where it only saves the dirty objects
-
Skagen00 You did not misunderstand and when I first read the post that indicated that I needed to mix Editable Root List and Editable Child, I was surprised, but I have learned that CSLA sometimes has surprising things and have mostly stopped questioning "why" and just try to understand "How". I know there is a post on this forum
-
Our project is using CSLA 4 and CodeSmith to generate. The task I have to solve is for a list of editable objects that can be used in a multi user situation. Each user will see the same list; however any one item will only be edited by one user. i.e. list of tasks to complete and each user of the system will only update his/her task. BUT, the UI will
-
I suppose. I am not meaning to be argumentative. It just seems flawed. To me IDataErrorInfo is an interface providing info about an error. The error and the message are decoupled and the interface just provides information. The error occurs regardless of the message -- such are the ways of pesky little errors. However, the CSLA usage seems to tightly
-
Speaking to an associate here and thinking on this some over night I would like assert that it isn't CSLA's scope to dictate usage for error messages. The link you provided to Microsoft does not indicate that a message is required; only that the default is empty string. The below statement, quoted from the link link you provided, is written
-
While I agree an empty string is not good for an actual error, we are just trying to get it working at the moment. If it is a MUST then perhaps a usable error should be thrown when empty string is passed instead of just swallowing the rule and returning true.
-
I'm back. So, we created a rule using the Lamda expression pretty much just like what Johnny Bee wrote on the second to the last line above. However, under no condition can we get the rule to fail. We even went as far as setting the comparison to false explicitly and no broken rules. We put break points on the Lamda and see the property values,