Is there a way to specify the isolation level of a transaction in BEEF?

[shirleywesley]

We are using BEEF core version 4 in our application. We would like to set the default isolation level of the TransactionScope to READ COMMITTED. We can see in https://github.com/Avanade/Beef/blob/version-4/src/Beef.Core/Business/BusinessInvokerBase.cs, we can pass argument TransactionScopeOption to WrapInvokeAsync but there appears to be no way to set TransactionOption argument which controls the isolation level. Isolation level in .net by default seems to be Serializable.

Commented code below is what we would like to do:

Any ideas of how we can do this? Thank you!

[chullybun]

Hi @shirleywesley, yes there is.

Within the base Invokerthe following code will look to load a generic TInvoker from the underlying IServiceProvider where configured, so that represents our runtime replacement opportunity:

protected static TInvoker GetCurrentInstance<TInvoker>(bool throwExceptionOnNull = true) where TInvoker : Invoker => ExecutionContext.GetService<TInvoker>(throwExceptionOnNull)!;

The DataInvoker, DataSvcInvoker and ManagerInvoker all implement code similar to:

    public class ManagerInvoker : BusinessInvokerBase
    {
        /// <summary>
        /// Gets the current configured instance (see <see cref="ExecutionContext.ServiceProvider"/>).
        /// </summary>
        public static ManagerInvoker Current => GetCurrentInstance<ManagerInvoker>(false) ?? new ManagerInvoker();
    }

What you'll need to do is create your own XxxDataInvoker, XxxDataSvcInvoker and XxxManagerInvoker classes all inheriting from their namesake. Then override all the base WrapInvoke and WrapInvokeAsync methods similar to BusinessInvokerBase - i.e. copy and paste into each and tweak to your requirements, or separate into a static helper and have each invoke to enable reuse 🙂 The key outcome is that they will no longer rely on the base implementation and will use your new shiny code.

The final step is then to register each at startup, i.e. services.AddSingleton<ManagerInvoker, XxxManagerInvoker>.

All going well this should work. Note I have not tested this; let me know if you run into any issues as there may be one other option to enable that is a little more heavy handed.

Cheers...

[shirleywesley]

Thanks again Eric, that seems to have worked for us!