LogicalExecutionLocation is confused by RunLocal Attribute

[GrantArgy]

I am trying to understand why LogicalExecutionLocation is different in the following two scenarios:

This is what my output is:

RunLocalTest.Create LogicalExecutionLocation: Server
RunLocalTest.Execute LogicalExecutionLocation: Server
EXECUTE LogicalExecutionLocation: Client
Test.Create LogicalExecutionLocation: Server
Test.Create LogicalExecutionLocation: Server
EXECUTE LogicalExecutionLocation: Server

These are the classes:

internal class Program
  {
    private static ServiceCollection _services;
    private static ServiceProvider _provider;
    private static ApplicationContext _context;
    static void Main(string[] args)
    {
      _services = new ServiceCollection();
      _services.AddCsla();
      _provider = _services.BuildServiceProvider();
      _context = _provider.GetRequiredService<ApplicationContext>();

      var localPortal = _provider.GetRequiredService<IDataPortal<RunLocalTest>>();
      var local = localPortal.Create();
      localPortal.Execute(local);

      var testPortal = _provider.GetRequiredService<IDataPortal<Test>>();
      var test = testPortal.Create();
      testPortal.Execute(test);

      Console.ReadLine();
    }

    internal static void TestMethod()
    {
      Console.WriteLine($"EXECUTE LogicalExecutionLocation: {_context.LogicalExecutionLocation}");
    }
  }

[Serializable]
  internal class RunLocalTest : Csla.CommandBase<RunLocalTest>
  {

    [Create]
    [RunLocal]
    private void CreateInternal()
    {
      Console.WriteLine($"RunLocalTest.Create LogicalExecutionLocation: {ApplicationContext.LogicalExecutionLocation}");
    }

    [Execute]
    private void ExecuteInternal()
    {
      Console.WriteLine($"RunLocalTest.Execute LogicalExecutionLocation: {ApplicationContext.LogicalExecutionLocation}");
      Program.TestMethod();
    }
  }

[Serializable]
  internal class Test : Csla.CommandBase<Test>
  {

    [Create]
    private void CreateInternal()
    {
      Console.WriteLine($"Test.Create LogicalExecutionLocation: {ApplicationContext.LogicalExecutionLocation}");
    }

    [Execute]
    private void ExecuteInternal()
    {
      Console.WriteLine($"Test.Create LogicalExecutionLocation: {ApplicationContext.LogicalExecutionLocation}");
      Program.TestMethod();
    }
  }

[rockfordlhotka]

In the RunLocal case, there are two DI scopes - the original client one in Program.cs and the temporary one created by the data portal.

In the remote case, there are three DI scopes. The original client one, a server one where the data portal is hosted, and the temporary one created by the data portal.

[GrantArgy]

Thanks, but therefore that won't help me. I am trying to determine whether a dataportal operation is being executed without the run local attribute. The reason for this is that I only want a call to a an sql connection manager in those cases to ensure it is on the server. The client should not have access.

[rockfordlhotka]

You probably want the physical execution location, not the logical location.

[GrantArgy]

Only problem is we have a configuration for both : use app server or not so when app server is run it would be ok but not the other way.

In that case sql is available locally