Matt Connew

For anyone watching this issue, I'm about to commit a large amount of code to the feature/wsdl branch to enable contribution of tests. There's a lot of cleanup I need...

@Danielku15, I finally had to get around to fixing the base address issue. Because of how ASP.NET Core handles mapping to a sub path, you don't find out what that...

@Danielku15, that's not a workable option. If you compare it to WCF, you might have a service with a base address `http://localhost/services/MyService.svc` with 2 endpoints defined. You could have an...

Sorry for the slow reply, I was taking a much needed break over the Christmas holiday. That's a bug for that binding, but you can still do what you want...

WCF targets .NET Standard 2.0 so our latest release will work on all currently supported versions of .NET Core. If you are using a custom binding, you don't need BasicHttpsBinding....

For your first problem, do you have it working using WCF on .NET Framework? Or are you using a web services client on .NET Framework and now trying to use...

@fptkolodziejczyk, for some reason I thought this would need an api change which can't happen in a patch release. But I just looked at the PR again and I'm not...

@fptkolodziejczyk, in regard to Re.2, I don't have enough information to say what's going on. The server is returning a 503 error, so there's something the server didn't like about...

We will update this, but FYI WCF client isn't vulnerable to this issue. I examined the problem the fix addresses and the WCF client doesn't have the vulnerable scenario. Basically,...

FYI there will be a small delay on this as we missed updating all our dependency versions in our last release so I want to evaluate and update everything to...