Matt Connew

I'll retitle this issue and can use this to track it.

The short answer is it won't be supported in the near term (next 18 months for certain). Below is a brief explanation of the technical problems that need to be...

I just realized I answered about IIS, Http.Sys is a different matter. I'll reply about that later today.

I had a fresh look at the implementation and you can't host multiple IServer instances (which is what Http.Sys and Kestrel both supply) in a single WebHost. If you want...

When the net.tcp port sharing feature is implemented, you will be able to do the approach listed above. A pre-requisite for net.tcp port sharing is NetNamedPipe binding on the WCF...

I have a path to getting Port Sharing working now due to some changes happening in .NET 6. But it's going to have to wait until we move to .NET...

@spur19, port sharing will require .NET 6 as there are new api's introduced in ASP.NET Core 6 to accommodate CoreWCF doing port sharing. Do you need TCP activation too (hosting...

The initial feature will definitely work by having two separate WebHostBuilder instances in the same process, but I need to get the scenario you want working as a step towards...

Net.Tcp port sharing isn't supported yet in CoreWCF. That feature will be coming at the start of next year. You could possibly use WCF Routing Services in .NET Framework as...

@brentschmaltz, is there a reason why the default here is different than NetFx? @Raschmann, as the api is there, setting it to true is supported. Does it work if you...