Guillaume Delahaye

> Hi! This is legacy from when stryker was not yet such a bug project. You are right that we should probably revisit and decide if it's time for dependency...

@mconnew what do you think about adding a roslyn analyzer that probe the existence of the new API in referenced assemblies using the semantic model and then report an appropriate...

A possible fix would be to introduce a `CustomMetadataAddressProviderBehavior` that pull a `IMetadataAddressProvider` from DI. This new behavior would bypass `UseRequestHeadersForMetadataAddressBehavior` if present in DI. This would bring full control...

Thanks @DentonCarr for reporting the issue. Indeed it seems there is a mismatch between https://github.com/CoreWCF/samples/blob/c7e40c56295474851af7cb61b7d5e3e1f34ebd06/Scenarios/Getting-Started-with-CoreWCF/NetCoreServer/Startup.cs#L49 and https://github.com/CoreWCF/samples/blob/c7e40c56295474851af7cb61b7d5e3e1f34ebd06/Scenarios/Getting-Started-with-CoreWCF/NetCoreClient/Program.cs#L77. would you be able to submit a pr in the CoreWCF/samples repo to...

``` ini BenchmarkDotNet=v0.13.1, OS=Windows 10.0.19044.1889 (21H2) Intel Xeon W-11955M CPU 2.60GHz, 1 CPU, 16 logical and 8 physical cores .NET SDK=6.0.400 [Host] : .NET 6.0.8 (6.0.822.36306), X64 RyuJIT VeryLongRun :...

An implementation relying on Apache Kafka would also be nice

I think a kind of cookbook with below recipes would also ease migration. Format could be simple code snippet in markdown or complete sample. - Use DI registered ServiceBehavior -...

CoreWCF brings server side support of WCF features with net6. Regarding client side you should still use System.ServiceModel.* nuget packages. Thus i think you should split your EndpointBehavior having one...

@jonlouie Why not taking a dependency to ASP.NET core using FrameworkReference ? please see https://docs.microsoft.com/en-us/aspnet/core/fundamentals/target-aspnetcore?view=aspnetcore-6.0&tabs=visual-studio#use-the-aspnet-core-shared-framework

@mconnew i see in the PR description that you aim to drop the Roslyn 3.11 Build.Tools, please do notice that this is not required to take the dependency on .NET...