Hong Li comments

Results 78 comments of


                                            Hong Li

Consuming WCF service using net named pipe binding in asp .net core 2.0 api

This feature is still in the plan to ship in .NET 7.0.

Visual Studio 16.8 breaks SvcUtil build targets

@imcarolwang can you please see what is the issue here?

Client can not be generated

@imcarolwang can you please try using the simple repro on .NET Core and .NET framework?

Client can not be generated

close due to no response, feel free to re-activate if this issue persists.

Compiling JScript/CSharp scripts is not supported.

@santo1991 this is not a great message. Usually, this happens when generating the serializer failed. Please attach debugger and find out what exception was thrown before this exception and share...

System.ServiceModel.Http v4.10

The workaround is to delete the `OurServiceNameClient.CloseAsync()`, and the fix is to fix dotnet-svcutil not to generate '`OurServiceNameClient.CloseAsync()`'.

A call to SSPI failed: The target principal name is incorrect

@mconnew could you please chime in?

The Content-Type for TextMessageEncoder doesn't support a whitespace character between content-type and charset, moreover the IsContentTypeSupported overload doesn't work

@Teugata this seems to be the same as .NET Framework. can you please try https://justsimplycode.com/2019/11/02/disable-header-100-continue-in-net-core-wcf-client/ to modify the content-type header after the response being received?

The Content-Type for TextMessageEncoder doesn't support a whitespace character between content-type and charset, moreover the IsContentTypeSupported overload doesn't work

Close this issue due to no response. Feel free to re-open if the issues persist after above suggestion.

The Content-Type for TextMessageEncoder doesn't support a whitespace character between content-type and charset, moreover the IsContentTypeSupported overload doesn't work

Reactivating for further investigation.