5.0.3 to 5.0.6: Method 'SomeMethod' on type 'SomeType' is not accessible.

[christophwille]

That was the inner exception message, the outer is "Error while compiling rule unittestrule2: Method 'SomeMethod' on type 'SomeType' is not accessible."

Can someone please point me to where RuleParameters have changed so drastically?

var rp = new RuleParameter("utils", new SomeType());
var resultList = await bre.ExecuteAllRulesAsync("Default", rp);

And of course the bre included the call to utils.SomeMethod.

[christophwille]

If found the difference - CustomTypes in ReSettings is now mandatory as of RulesEngine 5.0.6 (it worked fine in 5.0.3 without being specified)

            var reSettings = new ReSettings
            {
                EnableExceptionAsErrorMessage = false,
                IgnoreException = false,
                CustomTypes = new Type[]
                {
                    typeof(SomeType),
                },
                UseFastExpressionCompiler = false
            };

I found another difference in 5.0.6 to 5.0.3 - when eg SomeMethod threw an exception, there used to be a useful exception message on RuleException:

"Error while executing rule : nameofrulehere - innerexceptionmessagehere"

Now in 5.0.6 ex.Message is empty string although InnerException with innerexceptionmessagehere is still provided.

[asulwer]

@christophwille this fork is not being maintained

[christophwille]

And who is then pushing NuGet updates from this repository?

[asulwer]

no one is

[christophwille]

https://github.com/microsoft/RulesEngine/commits/main/ so @pbhal is "no one" apparently?

[pbhal]

@asulwer / @christophwille - We have allocated capacity within Microsoft to extend support to the library.

[pbhal]

@christophwille - With the new version, as a dependency arising out of upgrading System.Linq.Dynamic.Core, CustomTypes becomes mandatory to pass. Changelog : https://github.com/microsoft/RulesEngine/releases/tag/v5.0.6

Will be releaseing a minor version upgrade with the error message fix. Will keep the thread updated.

[asulwer]

@pbhal @abbasc52 what does the original maintainer say about this?

[abbasc52]

For inputs , type registration was mandatory since v5.0.0 and corresponding system.linq.dynamic.core. To minimize user impact, we started updating resettings at runtime. It seems the related code was recently updated which might have caused this issue -

RulesEngine/src/RulesEngine/RulesEngine.cs

Line 295 in b1264a2

_reSettings.CustomTypes.Safe().Union(ruleParams.Select(c => c.Type)).ToArray();

Maybe reverting back this code to previous version might fix method not accessible issue

[asulwer]

@abbasc52 i agree with your assessment. my fork has this solution plus additional fixes and features