Anders Mörner

I think that would require quite a bit of work. You are, of course, very welcome to give it a shot and submit a PR. I suggest forking the repository...

Hi, You'll have to fork the repo and submit a pull request from your repo to this one. Then we can merge your changes, if everything looks good!

That scenario is not supported and I don't think it can be support. It could result in conflicting namespaces, duplicate actions etc. You'll have to combine both of them, if...

Not sure I understand correctly. Are you having trouble getting requests from existing clients to work? If you need to keep supporting existing payloads, that doesn't work out of the...

There is no support for this scenario right now. You are welcome to submit a PR if you feel like giving it a shot yourself

https://github.com/DigDes/SoapCore/blob/b6ad1aae3fa70a2383c5e910ca8d957a31af62c7/src/SoapCore/SoapEndpointMiddleware.cs#L446 This is where the exception is thrown. So when UseBasicAuthentication is enabled the client tries to call the service with "http://schemas.xmlsoap.org/ws/2004/09/transfer/Get" as the action-parameter. According to https://specs.xmlsoap.org/ws/2004/09/transfer/WS-Transfer0904.pdf this is...

I definitely see the use case for this. What do you think about making the interface accept a `PathString` and return another `PathString`? The current design was already established, but...

Thanks again for this contribution. I'll give this another review as soon as you've had the time to fix the unit test and address the design issues we discussed

If you feel up for it, please submit a PR with a fix and a unit test that verifies the fix. We'll get it merged as soon as possible

This can be specified on the endpoint: ``` app.UseSoapEndpoint((opt) => { opt.Path = $"/MyService.asmx"; opt.OmitXmlDeclaration = false; }) ```