"System.ServiceModel.EndpointIdentity.CreateUpnIdentity" method for .net standard?
See original GitHub issueHello, unfortunately the method “System.ServiceModel.EndpointIdentity.CreateUpnIdentity” does not exist for .net standard 2.0. I need this method for creating a EndpointAddress:
EndpointAddress myEndpoint = new EndpointAddress(new Uri(wcfEndpoint.Endpoint), EndpointIdentity.CreateUpnIdentity(wcfEndpoint.Identity));
What can I do to make this also work on .net standard?
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
c# - EndpointIdentity does not contain a definition for ...
When converting a class library from .NET Framework 4.6.2 to .NET Standard 2.0 i get this error: "EndpointIdentity does not contain a definition...
Read more >EndpointIdentity.CreateUpnIdentity(String) Method
A secure WCF client that connects to an endpoint with this identity uses the UPN when performing SSPI authentication with the endpoint. This...
Read more >EndpointIdentity.cs source code in C# .NET
ServiceModel { using System; using System.Net; using System.Collections; using System.Collections.Generic; using System.Diagnostics; using System.
Read more >Invoking the PDF Converter Web Service from Visual ...
Once the service reference has been added you can either use the sample VB.NET code listed at the end of this post or...
Read more >Converting Office files to PDF Format using a Web Services ...
This makes it very simple to convert typical Office files to PDF format from your own .NET, Java or any other web services...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Try this:
As an aside, part of some of the pain and difficulty people have with using WCF is there’s about 20 ways to do the exact same thing. I’m trying to minimize that with the .NET Core implementation as much as is reasonable which sometimes means small but compatible code changes need to be done.