new-webserviceproxy

Why is powershell adding additional parameters to Web Service Method Signatures

孤者浪人 提交于 2019-12-23 09:59:43
问题 I'm trying to use Powershell to ping a couple of WCF Webservices from the command line. e.g. I have an WCF Operation [OperationContract] string DoWork(string name); And I can call that with Powershell using. $proxy = New-WebServiceProxy -Uri 'http://localhost/TestService/Service.svc' $proxy.DoWork('Hello World') This works fine as long as the input params and return types are strings. However if I introduce integers, the generated method signatures & return types have additional

Blazor WebAPI to Client deserialization exception (PocoJsonSerializerStrategy)

為{幸葍}努か 提交于 2019-12-13 23:55:59
问题 I am able to generate a proxy (using VS 2017) via the Microsoft OData Connector Service Nuget. This generates the proxy just fine. However, when i try to send a entity over the wire to the client side, i get a deserialization exception. Is there any technical issues using service reference/proxy generated entities/data-models? Below is the exception i was able to capture when the payload is retrieved from my Web API to the client. System.Reflection.TargetParameterCountException: Number of