Support for ASP.NET Core 3.0

What is the recommended way to use Castle Windsor with asp.net core 3.0? One place where it can integrated would be the generic host towards which asp.net core 3.0 migrated, probably using UseServiceProviderFactory

Using Castle.AspnetCore.Facility is no longer possible (or at least I didn’t found out how) because Startup.ConfigureServices returning IServiceProvider is no longer supported by the framework and AddWindsor cannot be used anymore. Before I used to write something like this in Startup class

public IServiceProvider ConfigureServices(IServiceCollection services)
{
    container.AddFacility<AspNetCoreFacility>(f => f.CrossWiresInto(services));
[...]
    return services.AddWindsor(container, 
        opts =>
         {
            opts.RegisterControllers(typeof(MyController).Assembly, LifestyleType.Transient);
         });
}

[chrisheil]

@generik0 We upgraded our application the day the beta came out, and have been cleared in QA and UAT after several months of testing. In fact, this beta resolved some issues we had faced with the workarounds we had introduced with the earlier solutions before the beta

We are running on asp.netcore 3.0 web api with the following:

• automapper
• castle dynamic proxy
• graylog
• Entity Framework Core 2.2
• FluentValidation

We are also upgrading another product to use this beta with similar dependencies, and early signs are positive

[jonorossi]

@generik0 It is best to create new issues to track things since this is already closed and released (as a beta).