WSHttpBinding in .NetStandard or .NET core
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I want to integrate NMVS protocol in my application which is providing wsdl files for testing which is written sample code in .net framework library.
I want to test it in .netstandard, .netcore or UWP app but wsdl files only support to "WSHttpBinding" which is not supported in .netstandard, .net core and UWP.
<wsdl:binding name="WSHttpBinding_ISinglePackServices" type="ns:ISinglePackServices">
WSHttpBinding binding = new WSHttpBinding();
binding.Security.Mode = SecurityMode.Transport;
binding.Security.Transport.ClientCredentialType = HttpClientCredentialType.Certificate;
I used basichttpbinding but I am getting error that says "The content type application/soap+xml; charset=UTF-8 of the response message does not match the content type of the binding (text/xml; charset=utf-8)."
What are the other ways to troubleshoot this issue?
Thanks
Imrankhan
asp.net-core uwp .net-standard wshttpbinding
add a comment |
I want to integrate NMVS protocol in my application which is providing wsdl files for testing which is written sample code in .net framework library.
I want to test it in .netstandard, .netcore or UWP app but wsdl files only support to "WSHttpBinding" which is not supported in .netstandard, .net core and UWP.
<wsdl:binding name="WSHttpBinding_ISinglePackServices" type="ns:ISinglePackServices">
WSHttpBinding binding = new WSHttpBinding();
binding.Security.Mode = SecurityMode.Transport;
binding.Security.Transport.ClientCredentialType = HttpClientCredentialType.Certificate;
I used basichttpbinding but I am getting error that says "The content type application/soap+xml; charset=UTF-8 of the response message does not match the content type of the binding (text/xml; charset=utf-8)."
What are the other ways to troubleshoot this issue?
Thanks
Imrankhan
asp.net-core uwp .net-standard wshttpbinding
WSDL is a SOAP standard. The WS binding means it supports the WS-* interoperability standards. That's what WCF uses. If you useAdd Service Reference
orAdd Connected Service
Visual Studio will create a WCF proxy that takes care of all this. Why are you trying to write the bindings by hand?
– Panagiotis Kanavos
Nov 15 '18 at 14:51
Which .NET Standard version are you trying to target? The older .NET Core/Standard versions didn't support all types required for WCF. The latest ones do. This means that even ifAdd Connected Services
doesn't work, you can generate the proxy in a Full Framework project, copy the files to a Standard 2.0 project, compile it and use it
– Panagiotis Kanavos
Nov 15 '18 at 14:55
NMVS has provided some .wsdl file that I have added using Add connected service. Now to call some methods I need to setup secure mode and client credential type that you can see above wshttpbinding code. and that xml part is from wsdl file.
– Imrankhan
Nov 15 '18 at 15:04
add a comment |
I want to integrate NMVS protocol in my application which is providing wsdl files for testing which is written sample code in .net framework library.
I want to test it in .netstandard, .netcore or UWP app but wsdl files only support to "WSHttpBinding" which is not supported in .netstandard, .net core and UWP.
<wsdl:binding name="WSHttpBinding_ISinglePackServices" type="ns:ISinglePackServices">
WSHttpBinding binding = new WSHttpBinding();
binding.Security.Mode = SecurityMode.Transport;
binding.Security.Transport.ClientCredentialType = HttpClientCredentialType.Certificate;
I used basichttpbinding but I am getting error that says "The content type application/soap+xml; charset=UTF-8 of the response message does not match the content type of the binding (text/xml; charset=utf-8)."
What are the other ways to troubleshoot this issue?
Thanks
Imrankhan
asp.net-core uwp .net-standard wshttpbinding
I want to integrate NMVS protocol in my application which is providing wsdl files for testing which is written sample code in .net framework library.
I want to test it in .netstandard, .netcore or UWP app but wsdl files only support to "WSHttpBinding" which is not supported in .netstandard, .net core and UWP.
<wsdl:binding name="WSHttpBinding_ISinglePackServices" type="ns:ISinglePackServices">
WSHttpBinding binding = new WSHttpBinding();
binding.Security.Mode = SecurityMode.Transport;
binding.Security.Transport.ClientCredentialType = HttpClientCredentialType.Certificate;
I used basichttpbinding but I am getting error that says "The content type application/soap+xml; charset=UTF-8 of the response message does not match the content type of the binding (text/xml; charset=utf-8)."
What are the other ways to troubleshoot this issue?
Thanks
Imrankhan
asp.net-core uwp .net-standard wshttpbinding
asp.net-core uwp .net-standard wshttpbinding
asked Nov 15 '18 at 14:43
ImrankhanImrankhan
284
284
WSDL is a SOAP standard. The WS binding means it supports the WS-* interoperability standards. That's what WCF uses. If you useAdd Service Reference
orAdd Connected Service
Visual Studio will create a WCF proxy that takes care of all this. Why are you trying to write the bindings by hand?
– Panagiotis Kanavos
Nov 15 '18 at 14:51
Which .NET Standard version are you trying to target? The older .NET Core/Standard versions didn't support all types required for WCF. The latest ones do. This means that even ifAdd Connected Services
doesn't work, you can generate the proxy in a Full Framework project, copy the files to a Standard 2.0 project, compile it and use it
– Panagiotis Kanavos
Nov 15 '18 at 14:55
NMVS has provided some .wsdl file that I have added using Add connected service. Now to call some methods I need to setup secure mode and client credential type that you can see above wshttpbinding code. and that xml part is from wsdl file.
– Imrankhan
Nov 15 '18 at 15:04
add a comment |
WSDL is a SOAP standard. The WS binding means it supports the WS-* interoperability standards. That's what WCF uses. If you useAdd Service Reference
orAdd Connected Service
Visual Studio will create a WCF proxy that takes care of all this. Why are you trying to write the bindings by hand?
– Panagiotis Kanavos
Nov 15 '18 at 14:51
Which .NET Standard version are you trying to target? The older .NET Core/Standard versions didn't support all types required for WCF. The latest ones do. This means that even ifAdd Connected Services
doesn't work, you can generate the proxy in a Full Framework project, copy the files to a Standard 2.0 project, compile it and use it
– Panagiotis Kanavos
Nov 15 '18 at 14:55
NMVS has provided some .wsdl file that I have added using Add connected service. Now to call some methods I need to setup secure mode and client credential type that you can see above wshttpbinding code. and that xml part is from wsdl file.
– Imrankhan
Nov 15 '18 at 15:04
WSDL is a SOAP standard. The WS binding means it supports the WS-* interoperability standards. That's what WCF uses. If you use
Add Service Reference
or Add Connected Service
Visual Studio will create a WCF proxy that takes care of all this. Why are you trying to write the bindings by hand?– Panagiotis Kanavos
Nov 15 '18 at 14:51
WSDL is a SOAP standard. The WS binding means it supports the WS-* interoperability standards. That's what WCF uses. If you use
Add Service Reference
or Add Connected Service
Visual Studio will create a WCF proxy that takes care of all this. Why are you trying to write the bindings by hand?– Panagiotis Kanavos
Nov 15 '18 at 14:51
Which .NET Standard version are you trying to target? The older .NET Core/Standard versions didn't support all types required for WCF. The latest ones do. This means that even if
Add Connected Services
doesn't work, you can generate the proxy in a Full Framework project, copy the files to a Standard 2.0 project, compile it and use it– Panagiotis Kanavos
Nov 15 '18 at 14:55
Which .NET Standard version are you trying to target? The older .NET Core/Standard versions didn't support all types required for WCF. The latest ones do. This means that even if
Add Connected Services
doesn't work, you can generate the proxy in a Full Framework project, copy the files to a Standard 2.0 project, compile it and use it– Panagiotis Kanavos
Nov 15 '18 at 14:55
NMVS has provided some .wsdl file that I have added using Add connected service. Now to call some methods I need to setup secure mode and client credential type that you can see above wshttpbinding code. and that xml part is from wsdl file.
– Imrankhan
Nov 15 '18 at 15:04
NMVS has provided some .wsdl file that I have added using Add connected service. Now to call some methods I need to setup secure mode and client credential type that you can see above wshttpbinding code. and that xml part is from wsdl file.
– Imrankhan
Nov 15 '18 at 15:04
add a comment |
1 Answer
1
active
oldest
votes
Here is a solution for your problem :
var transportSecurityBinding = new BasicHttpBinding();
transportSecurityBinding.Security.Mode = BasicHttpSecurityMode.Transport;
transportSecurityBinding.Security.Transport.ClientCredentialType = HttpClientCredentialType.Certificate;
var customTransportSecurityBinding = new CustomBinding(transportSecurityBinding);
var textBindingElement = new TextMessageEncodingBindingElement
MessageVersion = MessageVersion.CreateVersion(EnvelopeVersion.Soap12, AddressingVersion.None)
;
// Replace text element to have Soap12 message version
customTransportSecurityBinding.Elements[0] = textBindingElement;
Nicolas Giannone SPRL (https://www.facebook.com/Nicolas.Giannone.SPRL)
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53321927%2fwshttpbinding-in-netstandard-or-net-core%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Here is a solution for your problem :
var transportSecurityBinding = new BasicHttpBinding();
transportSecurityBinding.Security.Mode = BasicHttpSecurityMode.Transport;
transportSecurityBinding.Security.Transport.ClientCredentialType = HttpClientCredentialType.Certificate;
var customTransportSecurityBinding = new CustomBinding(transportSecurityBinding);
var textBindingElement = new TextMessageEncodingBindingElement
MessageVersion = MessageVersion.CreateVersion(EnvelopeVersion.Soap12, AddressingVersion.None)
;
// Replace text element to have Soap12 message version
customTransportSecurityBinding.Elements[0] = textBindingElement;
Nicolas Giannone SPRL (https://www.facebook.com/Nicolas.Giannone.SPRL)
add a comment |
Here is a solution for your problem :
var transportSecurityBinding = new BasicHttpBinding();
transportSecurityBinding.Security.Mode = BasicHttpSecurityMode.Transport;
transportSecurityBinding.Security.Transport.ClientCredentialType = HttpClientCredentialType.Certificate;
var customTransportSecurityBinding = new CustomBinding(transportSecurityBinding);
var textBindingElement = new TextMessageEncodingBindingElement
MessageVersion = MessageVersion.CreateVersion(EnvelopeVersion.Soap12, AddressingVersion.None)
;
// Replace text element to have Soap12 message version
customTransportSecurityBinding.Elements[0] = textBindingElement;
Nicolas Giannone SPRL (https://www.facebook.com/Nicolas.Giannone.SPRL)
add a comment |
Here is a solution for your problem :
var transportSecurityBinding = new BasicHttpBinding();
transportSecurityBinding.Security.Mode = BasicHttpSecurityMode.Transport;
transportSecurityBinding.Security.Transport.ClientCredentialType = HttpClientCredentialType.Certificate;
var customTransportSecurityBinding = new CustomBinding(transportSecurityBinding);
var textBindingElement = new TextMessageEncodingBindingElement
MessageVersion = MessageVersion.CreateVersion(EnvelopeVersion.Soap12, AddressingVersion.None)
;
// Replace text element to have Soap12 message version
customTransportSecurityBinding.Elements[0] = textBindingElement;
Nicolas Giannone SPRL (https://www.facebook.com/Nicolas.Giannone.SPRL)
Here is a solution for your problem :
var transportSecurityBinding = new BasicHttpBinding();
transportSecurityBinding.Security.Mode = BasicHttpSecurityMode.Transport;
transportSecurityBinding.Security.Transport.ClientCredentialType = HttpClientCredentialType.Certificate;
var customTransportSecurityBinding = new CustomBinding(transportSecurityBinding);
var textBindingElement = new TextMessageEncodingBindingElement
MessageVersion = MessageVersion.CreateVersion(EnvelopeVersion.Soap12, AddressingVersion.None)
;
// Replace text element to have Soap12 message version
customTransportSecurityBinding.Elements[0] = textBindingElement;
Nicolas Giannone SPRL (https://www.facebook.com/Nicolas.Giannone.SPRL)
answered Nov 16 '18 at 11:09
Nicolas GiannoneNicolas Giannone
611
611
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53321927%2fwshttpbinding-in-netstandard-or-net-core%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
WSDL is a SOAP standard. The WS binding means it supports the WS-* interoperability standards. That's what WCF uses. If you use
Add Service Reference
orAdd Connected Service
Visual Studio will create a WCF proxy that takes care of all this. Why are you trying to write the bindings by hand?– Panagiotis Kanavos
Nov 15 '18 at 14:51
Which .NET Standard version are you trying to target? The older .NET Core/Standard versions didn't support all types required for WCF. The latest ones do. This means that even if
Add Connected Services
doesn't work, you can generate the proxy in a Full Framework project, copy the files to a Standard 2.0 project, compile it and use it– Panagiotis Kanavos
Nov 15 '18 at 14:55
NMVS has provided some .wsdl file that I have added using Add connected service. Now to call some methods I need to setup secure mode and client credential type that you can see above wshttpbinding code. and that xml part is from wsdl file.
– Imrankhan
Nov 15 '18 at 15:04