This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
There was a post (http://www.mindscapehq.com/forums/thread/342487) from last year discussing a method of being able to add new records after UnitOfWork.SaveChanges has been called; I am looking for a basic alternative to setting up a repository model and this would fulfill my requirements. Has there been any progress made on this issue? It would be great if it were implemented as an override like Entity OnSaving. (Perhaps, OnBeforeSaving?) Thanks |
|
|
Yes the event mentioned has been available in all builds since then if you enable the CandidateFixes compatibility option as discussed in that thread.
|
|
|
Thanks |
|
|
re 1: No, we are planning on leaving this as it is currently implemented at this stage but we are open to reviewing this. re 2: Yes - Ive had a quick discussion here and we are happy to expose this as a standard option now so Ive added a commit to remove the requirement for the CandidateFixes flag which will be available in the next nightly build re 3: This flag enables any hot-fixes that we are testing with people who actually need the changed behavior prior to making it standard. There isnt a specific list of whats enabled that we circulate but you can roughly derive this from the forum threads where this is mentioned.
|
|