Business rules - stop triggering

[BlagoCuljak]

Hello everyone!

Since the upgrade to CSLA 5x, we are occasionaly experiencing a very strange (and dangerous...) rules behavior. Namely, without any apparent reason all of the business rules stop triggering completely. I am not talking about a single busines object here, but – to be clear – once this happens all of the objects (unrelated to the one where the problem started) are affected. Only after shutting down the entire application and starting it again normal behavior is restored. It happens very rarely and we cannot reproduce the issue, but I kind of hope someone here has at least some vague idea what could possibly cause such unexpected and undesirable effects.

[rockfordlhotka]

What kind of app?

[BlagoCuljak]

Well, just to let you know that we are still having issues, removed the async rules, upgraded WPF to 4.7.2, no logs or errors when this happens. We have reproduces this twice in VS, but no error is thrown. The app just doesn't compute as it should.

We are desperate, and we will include CSLA as project with code, not as NuGet, but we are not sure if we will pinpoint the issue in that way.

[rockfordlhotka]

Referencing CSLA directly may help. You might put console.writeline (or other log) statements into the code that executes the rules to help see what's happening? Since this is not repeatable, using break points in the debugger probably won't be efficient.

It isn't clear to me how I can help until the problem is narrowed down, but I'll help when possible.

[BlagoCuljak]

Well, we found culprit.. One Async rule had error, and although it had been in try/catch, on that one rule, we didn't logged error. Talk about bad luck.

It's all good once again.

[rockfordlhotka]

@BlagoCuljak do you think there is anything CSLA could have done to help make this more obvious?

[BlagoCuljak]

I don't think so. This was essential mistake in out code and arguments that Rule was working with.

Bad code review, no logging in catch, and so on.

Although same rule did work in 4.7, we are glad that this issue was brought to us when we updated to 5.x.

Good job Rocky (as always).