Matt Connew

Does the solution in #713 work for you?

I just added a comit to fix the breaking test.

Leaving open for community contribution as this is a case of a failing scenario failing the wrong way rather than a successful scenario failing so is lower priority.

@brentschmaltz, this issue is for tracking the WSTrustChannelFactory work you have started the design for.

Unfortunately this was necessary as the HTTP hosting model is different for asp.net core compared with .NET Framework. The problem we were having is when using app.Map("/path"), we were rejecting...

There are several walkthroughs that exist, can you link to the one you are following?

@ismaelhamed, can you open a new issue as that's a different problem. Can you provide the binding that you are using so I can reproduce the issue and write a...

I presumed this was a regression from .NET Framework, but after comparing the code with .NET Framework, I checked what the behavior is on .NET Framework with a test app...

For now the fastest path to a solution is to run multiple ASP.NET Core instances in the same app, one per port. This is similar to running a separate ServiceHost...

This method is needed for full Message security. We only support Transport and TransportWithMessageCredentials. We have some blocking dependencies at the moment which means this won't be available for quite...