Problems using Microsoft.Data.SqlClient in custom c# Powershell CmdLet

I run into a version conflict when trying to write my own CmdLet in C# (.NET Framework 4.7.2) using Microsoft.Data.SqlCLient - just these few lines of code are always resulting in some errors because SqlClient wants to load System.Memory version 4.0.1.1 - I need this dll for other nuget packages and have updated to latest version - I found no solution how to prevent SqlClient to use the old version of System.Memory

public class CmdLetEnvironment
{
    public static bool Connected = false;

    [System.Management.Automation.Cmdlet(System.Management.Automation.VerbsCommunications.Connect, "RDTest")]
    public class RDEnvironmentConnectCommand : System.Management.Automation.PSCmdlet
    {
        protected override void ProcessRecord()
        {
            try
            {
                SqlConnection conn = new SqlConnection("Data Source=localhost\\SQLEXPRESS;Initial Catalog=TestLocalOMA1;Integrated Security=True;Encrypt=False");
                conn.Open();
            }
            catch(Exception ex)
            {
                throw ex.InnerException;
            }
        }
    }
}

This is the error I always get:

> Could not load file or assembly 'System.Memory, Version=4.0.1.1, Culture=neutral,
PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The system cannot find the file specified.

Any help on this issue? I have tried so many different things (like app.config settings) but nothing seems to work

I found the solution for it - as Powershell is loading modules in different way then normal .NET application you need to override the assembly loading.

Add a constructor to the class and override AssemblyResolve to fix it - then you only need to ensure that all dll's are located in same directory then your CmdLet dll

[System.Management.Automation.Cmdlet(System.Management.Automation.VerbsCommunications.Connect, "RDTest")]
public class RDEnvironmentConnectCommand : System.Management.Automation.PSCmdlet
{
        public RDEnvironmentConnectCommand()
        {
            var domain = AppDomain.CurrentDomain;
            domain.AssemblyResolve += LoadAssembly;
        }

        private Assembly LoadAssembly(object sender, ResolveEventArgs args)
        {
            Assembly result = null;

                //Get current dll fullpath
                FileInfo info = new FileInfo(Assembly.GetExecutingAssembly().Location);

                //Get folder of the executing .exe
                var folderPath = info.Directory.FullName;

                //Build potential fullpath to the loading assembly
                var assemblyName = args.Name.Split(new string[] { "," }, StringSplitOptions.None)[0];
                var assemblyExtension = "dll";
                var assemblyPath = Path.Combine(folderPath, string.Format("{0}.{1}", assemblyName, assemblyExtension));


                if (File.Exists(assemblyPath))
                {
                    //Load the required assembly using our custom path
                    result = Assembly.LoadFrom(assemblyPath);
                }
                else
                {
                    //Keep default loading
                    return args.RequestingAssembly;
                }

            return result;
        }

    protected override void ProcessRecord()
    {
        try
        {
            SqlConnection conn = new SqlConnection("Data Source=localhost\\SQLEXPRESS;Initial Catalog=TestLocalOMA1;Integrated Security=True;Encrypt=False");
            conn.Open();
        }
        catch(Exception ex)
        {
            throw ex.InnerException;
        }
    }
}

I hope that could help other people running into the same issue