You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been trying to use WCF in a .net core 2.0 project, for 2 days without luck. I have a StackOverflow question with all my tries and problems but I´m stuck! I just can´t reproduce my old code in .net Core.
Is it even possible to use ClientCredentialType.UserName í .net Core project?
And how is it done?
If only there were more tests. This unittest is basically the only thing I found and its quite basic.
Thank you so much @zhenlan. My fault not finding these tests. I tried to search for them but maybe I did´t find them because I did´t know what to search for. The barrier to entry to WCF if quite high, especially if you don´t touch it often (years apart). I tried to amend that by answering my own question on StackOverflow and point to the resources needed to solve my problem. Please feel free to add to that answer if you have some other resources we should know about.
But thank you for your help. It was much appreciated!
P.s
I thought the code in the unittests you pointed out worked but I experienced the exception here below when fully implementing it (in async)
I have been trying to use WCF in a .net core 2.0 project, for 2 days without luck. I have a StackOverflow question with all my tries and problems but I´m stuck! I just can´t reproduce my old code in .net Core.
Is it even possible to use ClientCredentialType.UserName í .net Core project?
And how is it done?
If only there were more tests. This unittest is basically the only thing I found and its quite basic.
I so hope somebody here can help me.
dotnet --info
.NET Command Line Tools (2.1.4)
Product Information:
Version: 2.1.4
Commit SHA-1 hash: 5e8add2190
Runtime Environment:
OS Name: Windows
OS Version: 10.0.16299
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\2.1.4\
The text was updated successfully, but these errors were encountered: