-
Thanks Jonny, The truth is that the reason why we needed to have a way to detect when a cancel edit was in progress was due to some special circumstances, and after looking further into the matter we are pretty sure there are probably better ways to handle our scenario so that we don't have to rely on such flag. As of now, you solution helps us
-
Jonny, Sorry for my late response, I got caught up with some other stuff and was unable to follow up on your response until just some time ago. I tried your suggestion and it worked great (thank you very much), nevertheless, something does not feel right with what I am doing. The reason I say this is because is my understanding that the CSLA preferred
-
Hello, I have a couple of objects where I override the OnPropertyChanged and OnChildChanged functions. All is good until I call the “CancelEdit()” fuction because “CancelEdit()” will eventually trigger a call to the OnPropertyChanged and OnChildChanged functions and I have code on the OnPropertyChanged and OnChildChanged function
-
Thanks Jonny, If is no big deal, could you please post the code with the fix you guys came up? I would like to copy / paste your fix into the CSLA version we are currently using. We will eventually upgrade to the newest CSLA version but this is not the right time for us to do that. Thanks.
-
Rocky / Jonny I think I may have the cause of the problem but you guys will need to verify my assumption, these multithreading issues are real brain teasers I believe the issue has to do with the way you guys are trying to optimize the call to the "InitializeBusinessRules()" function (the double checked locking optimization). I have copied
-
I just tried to run the application with the latest version of the CSLA (4.3.13) and the problem still persist. So fix 1047 and 1026 do not fix this particular problem. The latest crash that we experienced happened when trying to enumerate the "TypeAuthRules.Rules" collection: public bool HasPermission(AuthorizationActions action, Csla.Core
-
Thanks Jonny. I don't want to mess around with upgrading the CSLA to a newer version at this time so I did't test our current code with the version you suggested. However, I did take a couple of minutes to try to replicate the error we are having and managed to crash the code on two different places. I am posting the crash information here to
-
We are currently using version 4.2.2.0 on a WPF application. Yes, we have many rules attached to the properties both business and authorization rules.
-
Hello. I am very much aware that interacting with one CSLA business object instance from multiple threads can lead to concurrency issues, but what I wasn't expecting was to run into concurrency issues when interacting with multiple CSLA business object instances all running on individual threads. Rather than trying to explain the issue with words
-
Rocky, No worries, keep up the good work, I certainly appreciate your efforts and patient... You know, I still remember picking up that Visual Basic 6 Business Objects book oh so many years ago (I think I got it from the Borders bookstore) it was a life changing event for me, you have been an inspiration to many of us and will always be number one in