Updating Windsor to support Castle.Core@5.0.0 and modern TFMs

With the release of Castle.Core@5.0.0, Windsor needs updating to support it as there are breaking changes (some detail in #610). 5.0.0 also has an updated list of TFMs:

<TargetFrameworks>net462;netstandard2.0;netstandard2.1;net6.0</TargetFrameworks>

The current targets for Windsor are:

Castle.Facilities.AspNet.Mvc = net45
Castle.Facilities.AspNet.Mvc.Tests = net45
Castle.Facilities.AspNet.SystemWeb = net45
Castle.Facilities.AspNet.SystemWeb.Tests = net45
Castle.Facilities.AspNet.WebApi = net45
Castle.Facilities.AspNet.WebApi.Tests = net45
Castle.Facilities.AspNetCore = netstandard2.0
Castle.Facilities.AspNetCore.Tests = netcoreapp2.0
Castle.Facilities.Logging = net45; netstandard2.0
Castle.Facilities.WcfIntegration = net45
Castle.Facilities.WcfIntegration.Demo = net45
Castle.Facilities.WcfIntegration.Tests = net45
Castle.Windsor = net45; netstandard2.0
Castle.Windsor.Extensions.DependencyInjection = netstandard2.0
Castle.Windsor.Extensions.DependencyInjection.Tests = net5.0; 
Castle.Windsor.Tests = net45; net5.0

Having not done much with the Windsor codebase, is it insane to suggest aligning with the Core TFM list, where reasonable? Does targeting net6.0 even make sense for Windsor? At the very least, it should support net462;netstandard2.0 against Castle.Core@5.0.0, which might be a good first step.

Could also consider retiring some of the Facilities, download counts don’t always set the world on fire (https://www.nuget.org/packages/Castle.Facilities.AspNet.Mvc/, https://www.nuget.org/packages/Castle.Facilities.AspNet.WebApi/).

[rsr-maersk]

Any luck here with a new build here. Latest Moq gives: on integration tests with: _container = new WindsorContainer();

[Jevonius]

Yeah, it’s a pain there’s such a critical issue with no workaround. Hopefully there will be some progress soon 😃