Daniel Setser

@nicoclau Sorry for not responding to this sooner, and thank you for reporting it. This sounds like it most likely has the same root cause as #3812, which is that...

@hurrk Old services like this are something we make a best effort to support with the connected service, but we've seen people running into issues with them. We can try...

We had another request for this feature in another issue, and there have been a couple more comments and reactions since we triaged this. Moving it to pri 2 instead...

@markecw We don't have time to fix this in the current milestone, so I can't give you any expected release yet. It sounds like you have a workaround that gives...

@mryandot Thanks for providing enough information for us to investigate this. It looks like the XML returned from the service does not match the current wsdl, and the behavior of...

This is a purposeful change between svcutil.exe and dotnet-svcutil.exe that was made because dotnet-svcutil was written to support .NET Core 1.0 apps, and these System.Data APIs were not available in...

We had another report of this issue on #3932. As part of investigating that developer community issue I looked into this a little more, and it's not as easy as...

@scrodde Since this issue is for the product rather than the documentation please open an issue on the WCF Core Github: https://github.com/dotnet/wcf/. When you open that issue can you also...

@Ramin2c This sounds similar to the original svcutil's /dataContractOnly argument. Would adding that option to dotnet-svcutil give you what you're looking for?

@imcarolwang Can you look into reproducing this?