Lamar compilation failure with AspNetCore Healthchecks UI

[sstrink]

I have an existing aspnetcore solution, 2.2.105 sdk, using Lamar and I recently added the new healthcheck api to my solution. I am using the 2.1.0 version of Lamar with the latest version of the healthchecks api (2.2.x) and healthchecks ui (2.2.19) projects.

In my ConfigureContainer method I am registering healthchecks for redis, sql server, and publishing to application insights.

       services.AddHealthChecks()
            .AddApplicationInsightsPublisher()
            .AddSqlServer(...)
            .AddRedis(...)

Then adding

        services.AddHealthChecksUI();

In my Configure method I register the following hooks:

        app.UseHealthChecks("/hc",
            new HealthCheckOptions
            {
                Predicate = hc => true,
                ResponseWriter = UIResponseWriter.WriteHealthCheckUIResponse
            });

        app.UseHealthChecks("/hc-cache",
            new HealthCheckOptions
            {
                Predicate = hc => hc.Tags.Contains("cache"),
                ResponseWriter = UIResponseWriter.WriteHealthCheckUIResponse
            });

        app.UseHealthChecks("/hc-db",
            new HealthCheckOptions
            {
                Predicate = hc => hc.Tags.Contains("database"),
                ResponseWriter = UIResponseWriter.WriteHealthCheckUIResponse
            });

        app.UseHealthChecks("/hc-domain",
            new HealthCheckOptions
            {
                Predicate = hc => hc.Tags.Contains("domainservice"),
                ResponseWriter = UIResponseWriter.WriteHealthCheckUIResponse
            });

        app.UseHealthChecksUI(opts => opts.UIPath = "/hc-ui");

The healthcheck UI calls a service with the route /healthchecks-api that returns all of the above healthcheck urls I register. When Lamar is used I receive the following error in my output from the healthchecks-api call. If Lamar is removed from the solution, the healthchecks api and UI work fine.

Microsoft.AspNetCore.Hosting.Internal.WebHost:Information: Request starting HTTP/1.1 GET http://localhost:17811/healthchecks-api
Microsoft.AspNetCore.HostFiltering.HostFilteringMiddleware:Trace: All hosts are allowed. Microsoft.AspNetCore.Routing.Matching.DfaMatcher:Debug: No candidates found for the request path '/healthchecks-api' Microsoft.AspNetCore.Routing.EndpointRoutingMiddleware:Debug: Request did not match any endpoints Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware:Debug: The request path does not match the path filter Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware:Error: An unhandled exception has occurred while executing the request.

System.InvalidOperationException: Compilation failures!

CS0122: 'HealthChecksDb' is inaccessible due to its protection level

Code:

using System; using System.Threading.Tasks;

namespace Jasper.Generated { // START: HealthChecks_UI_Core_Data_HealthChecksDb_healthChecksDb public class HealthChecks_UI_Core_Data_HealthChecksDb_healthChecksDb : Lamar.IoC.Resolvers.ScopedResolver

[jeremydmiller]

I hate the aspnet core team is my first thought here. This isn't going to get fixed quickly if you need to switch IoC tools. Lamar's basic model doesn't deal well with internal types and I honestly didn't realize how prevalent the usage of internal types in IoC containers was before I built Lamar.