Unable to use both EF Core 2.1 and ADOMD.NET together in either V1 or V2

[f2bo]

We need to implement a function that requires both Microsoft.EntityFrameworkCore v2.1 as well as the Microsoft.AnalysisServices.AdomdClient but it seems that this particular combination is not currently supported by either V1 or V2.

The AdomdClient package can be used successfully in a V1 function app. However, this is not the case for EF Core and any attempt to use it fails with a FileNotFoundException (Could not load file or assembly 'System.ComponentModel.Annotations, Version=4.2.0.0, ...').

When the same code is moved to a V2 function app, the EF Core code starts to work, but the AdomdClient fails with a TypeLoadException (Could not load type 'System.Security.Principal.WindowsImpersonationContext' from assembly 'mscorlib, Version=4.0.0.0, ...'). Note that when you add the AdomdClient package to the V2 project, you do get a warning alerting that this package targets .NET Framework, not .NET Standard and, presumably, WindowsImpersonationContext is not implemented in .NET Core, thus the failure.

Package 'Microsoft.AnalysisServices.AdomdClient.retail.amd64 15.3.1' was restored using '.NETFramework,Version=v4.6.1' instead of the project target framework '.NETStandard,Version=v2.0'. This package may not be fully compatible with your project.

Is there any workaround that will allow this scenario to fully work in either V1 or V2 or do we have to abandon Azure Functions?

Steps to reproduce

Create V1 and V2 function apps and configure them as follows:

NOTE: For the V2 App, the EF Core code fails when launched using the runtime currently used by the Function Tools in Visual Studio. However, it runs successfully when configured with the latest beta as described here:
How to manually update the Azure Functions Core Tools

1. Add the Microsoft.EntityFrameworkCore.InMemory v2.1 NuGet package
2. Add the Microsoft.AnalysisServices.AdomdClient NuGet package
3. Add some EF code.

    public class Person
    {
        public int Id { get; set; }
        public string Name { get; set; }
    }

    public class MyDbContext : DbContext
    {
        public DbSet<Person> People { get; set; }

        protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
        {
            optionsBuilder.UseInMemoryDatabase("test");
        }

        protected override void OnModelCreating(ModelBuilder modelBuilder)
        {
            modelBuilder.Entity<Person>().HasData(
                new Person { Id = 1, Name = "AAAA" },
                new Person { Id = 2, Name = "BBBB" },
                new Person { Id = 3, Name = "CCCC" }
            );
        }
    }

1. Use this function for the V1 app:

        [FunctionName("FunctionV1")]
        public static async Task<HttpResponseMessage> Run(
            [HttpTrigger(AuthorizationLevel.Function, "get", "post", Route = null)]
            HttpRequestMessage req,
            TraceWriter log)
        {
            // **** THIS EXECUTES SUCCESSFULLY IN V1
            using (var connection =
                new Microsoft.AnalysisServices.AdomdClient.AdomdConnection("Provider=MSOLAP;Data Source=localhost"))
            {
                connection.Open();
            }

            // **** THIS FAILS IN V1
            using (var context = new MyDbContext())
            {
                context.Database.EnsureDeleted();
                context.Database.EnsureCreated();
                var data = string.Join(", ", context.People.Select(p => p.Name));
            }

            return req.CreateResponse(HttpStatusCode.OK, "Completed!");
        }

1. Use this function for the V2 app:

        [FunctionName("FunctionV2")]
        public static IActionResult Run(
            [HttpTrigger(AuthorizationLevel.Function, "get", "post", Route = null)]HttpRequest req,
            TraceWriter log)
        {
            // **** THIS EXECUTES SUCCESSFULLY IN V2
            using (var context = new MyDbContext())
            {
                context.Database.EnsureDeleted();
                context.Database.EnsureCreated();
                var data = string.Join(", ", context.People.Select(p => p.Name));
            }

            // **** THIS FAILS IN V2
            using (var connection =
                new Microsoft.AnalysisServices.AdomdClient.AdomdConnection("Provider=MSOLAP;Data Source=localhost"))
            {
                connection.Open();
            }

            return (ActionResult)new OkObjectResult("Completed!");
        }

1. Run both functions.

The following exception is raised in the V1 app.

System.IO.FileNotFoundException: Could not load file or assembly 'System.ComponentModel.Annotations, Version=4.2.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
File name: 'System.ComponentModel.Annotations, Version=4.2.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
   at Microsoft.EntityFrameworkCore.Metadata.Conventions.Internal.CoreConventionSetBuilder.CreateConventionSet()
   at Microsoft.EntityFrameworkCore.Infrastructure.ModelSource.CreateConventionSet(IConventionSetBuilder conventionSetBuilder)
   at Microsoft.EntityFrameworkCore.Infrastructure.ModelSource.CreateModel(DbContext context, IConventionSetBuilder conventionSetBuilder, IModelValidator validator)
   at Microsoft.EntityFrameworkCore.Infrastructure.ModelSource.<>c__DisplayClass5_0.<GetModel>b__1()
   at System.Lazy`1.CreateValue()
   at System.Lazy`1.LazyInitValue()
   at System.Lazy`1.get_Value()
   at Microsoft.EntityFrameworkCore.Infrastructure.ModelSource.GetModel(DbContext context, IConventionSetBuilder conventionSetBuilder, IModelValidator validator)
   at Microsoft.EntityFrameworkCore.Internal.DbContextServices.CreateModel()
   at Microsoft.EntityFrameworkCore.Internal.DbContextServices.get_Model()
   at Microsoft.EntityFrameworkCore.Infrastructure.EntityFrameworkServicesBuilder.<>c.<TryAddCoreServices>b__7_1(IServiceProvider p)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitFactory(FactoryCallSite factoryCallSite, ServiceProviderEngineScope scope)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(ScopedCallSite scopedCallSite, ServiceProviderEngineScope scope)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, ServiceProviderEngineScope scope)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(ScopedCallSite scopedCallSite, ServiceProviderEngineScope scope)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.DynamicServiceProviderEngine.<>c__DisplayClass1_0.<RealizeService>b__0(ServiceProviderEngineScope scope)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngine.GetService(Type serviceType, ServiceProviderEngineScope serviceProviderEngineScope)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.GetService(Type serviceType)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService[T](IServiceProvider provider)
   at Microsoft.EntityFrameworkCore.DbContext.get_DbContextDependencies()
   at Microsoft.EntityFrameworkCore.DbContext.get_InternalServiceProvider()
   at Microsoft.EntityFrameworkCore.DbContext.Microsoft.EntityFrameworkCore.Infrastructure.IInfrastructure<System.IServiceProvider>.get_Instance()
   at Microsoft.EntityFrameworkCore.Internal.InternalAccessorExtensions.GetService[TService](IInfrastructure`1 accessor)
   at Microsoft.EntityFrameworkCore.Infrastructure.AccessorExtensions.GetService[TService](IInfrastructure`1 accessor)
   at Microsoft.EntityFrameworkCore.Infrastructure.DatabaseFacade.get_ProviderName()
   at Microsoft.EntityFrameworkCore.InMemoryDatabaseFacadeExtensions.IsInMemory(DatabaseFacade database)
   at StatsEngine.Metadata.StatsEngineDbContextFactory.Create(DbContextOptions`1 overrideOptions)
   at StatsEngine.Metadata.StatsEngineData.<GetAccumulatorsAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at AzureFunctionsV1.Function1.<Run>d__2.MoveNext()

=== Pre-bind state information ===
LOG: DisplayName = System.ComponentModel.Annotations, Version=4.2.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 (Fully-specified)
LOG: Appbase = file:///C:/Users/Fernando/AppData/Local/AzureFunctionsTools/Releases/1.3.0/cli/
LOG: Initial PrivatePath = NULL
Calling assembly : Microsoft.EntityFrameworkCore, Version=2.1.1.0, Culture=neutral, PublicKeyToken=adb9793829ddae60.
===
LOG: This bind starts in LoadFrom load context.
WRN: Native image will not be probed in LoadFrom context. Native image will only be probed in default load context, like with Assembly.Load().
LOG: Using application configuration file: C:\Users\Fernando\AppData\Local\AzureFunctionsTools\Releases\1.3.0\cli\func.exe.Config
LOG: Using host configuration file: 
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine.config.
LOG: Post-policy reference: System.ComponentModel.Annotations, Version=4.2.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
LOG: Attempting download of new URL file:///C:/Users/Fernando/AppData/Local/AzureFunctionsTools/Releases/1.3.0/cli/System.ComponentModel.Annotations.DLL.
LOG: Attempting download of new URL file:///C:/Users/Fernando/AppData/Local/AzureFunctionsTools/Releases/1.3.0/cli/System.ComponentModel.Annotations/System.ComponentModel.Annotations.DLL.
LOG: Attempting download of new URL file:///C:/Users/Fernando/AppData/Local/AzureFunctionsTools/Releases/1.3.0/cli/System.ComponentModel.Annotations.EXE.
LOG: Attempting download of new URL file:///C:/Users/Fernando/AppData/Local/AzureFunctionsTools/Releases/1.3.0/cli/System.ComponentModel.Annotations/System.ComponentModel.Annotations.EXE.
LOG: Attempting download of new URL file:///C:/projects/AzureFunctionsV1/bin/Debug/net472/bin/System.ComponentModel.Annotations.DLL.
WRN: Comparing the assembly name resulted in the mismatch: Build Number
LOG: Attempting download of new URL file:///C:/projects/AzureFunctionsV1/bin/Debug/net472/bin/System.ComponentModel.Annotations/System.ComponentModel.Annotations.DLL.
LOG: Attempting download of new URL file:///C:/projects/MetadataEFCore/AzureFunctionsV1/bin/Debug/net472/bin/System.ComponentModel.Annotations.EXE.
LOG: Attempting download of new URL file:///C:/projects/AzureFunctionsV1/bin/Debug/net472/bin/System.ComponentModel.Annotations/System.ComponentModel.Annotations.EXE.

The following exception is raised in the V2 app.

System.TypeLoadException: Could not load type 'System.Security.Principal.WindowsImpersonationContext' from assembly 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.
   at Microsoft.AnalysisServices.AdomdClient.IdentityResolver.Dispose()
   at Microsoft.AnalysisServices.AdomdClient.XmlaClient.Connect(ConnectionInfo connectionInfo, Boolean beginSession)
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Connect(Boolean toIXMLA)
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.ConnectToXMLA(Boolean createSession, Boolean isHTTP)
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.Open()
   at FunctionAppV2.Function1.Run(HttpRequest req, TraceWriter log) in C:\projects\FunctionAppV2\Function1.cs:line 31

Further technical details

V1 Functions runtime version: 1.0.11913.0
V2 Functions runtime version: 2.0.11888.0
Azure Functions and Web Jobs Tools: 15.0.40617.0
Microsoft.EntityFramework.Core version: 2.1.1
Microsoft.AnalysisServices.AdomdClient: 15.3.1
IDE: Visual Studio 2017: 15.7.5

[f2bo]

I managed to get this working in V1 by hooking the AppDomain.AssemblyResolve event and loading System.ComponentModel.Annotations but I'm not very confident that this is the way to go. I would appreciate some guidance from the team.

In any case, I've created a PR in the functions-assembly-loading-catalog repo with this scenario:

paulbatum/functions-assembly-loading-catalog#5

[paulbatum]

cc @fabiocav

Thanks for this report. Yes, it is expected that you would have issues with this scenario in both V1 and V2 - V1 because of the limitations in Functions itself, and V2 because you are using a library that only works on full framework, and we do not provide the option to run V2 on full framework within Azure (nor do we have any current plans to do so).

I see that there was a comment left on this page about the availability of a version of the analysis services client that runs on .NET core, but there are no replies.
https://docs.microsoft.com/en-us/sql/analysis-services/multidimensional-models/adomd-net/developing-with-adomd-net?view=sql-server-2017

Similarly, nothing particularly useful on this Stack Overflow post:
https://stackoverflow.com/questions/40969428/connect-with-net-core-to-ssas

I know you have the scenario working in V1 with a workaround, but honestly I am reluctant to recommend that you use Azure Functions for this scenario until we at least get an indication that the scenario of connecting to Analysis Services from .NET Core is going to be unblocked. Because at some point, V1 will transition into "critical/security fixes only" mode and at that point you will be at a dead end if no progress has been made on modernizing the Analysis Services connectivity story.

[f2bo]

I appreciate the response. I was hoping for better news but at least now we know where we stand. Frankly, I'm not very hopeful that the Analysis Services client will be updated any time soon. They don't even support async methods, but that's another story. It's a pity because otherwise, Azure Functions seemed like a really good fit.

Thanks!

[paulbatum]

For the sake of completeness, further discussion of running Functions V2 on full framework is here:
Azure/Azure-Functions#790

[fabiocav]

Closing this as answered, but please let us know if you have any additional questions/issues.