Closed samsp-msft closed 2 years ago
Should we have a .sln file in Basic\Binding\WS for the client and server to be in the same solution? Also the naming of WS should always have the S uppercase too. Eg our binding is WSHttpBinding and not WsHttpBinding.
We need a policy for sln files - is there only one at the root - or one per scenario? Having the client and server in the same sln is not that useful as you can't easily start both when like that, and if you do, the timing can be off so it won't work the way you think it should.
@mconnew the client is failing at the call to the service with:
And I can't figure out why?