http://developers.de/blogs/damir_dobric/archive/2008/04/18/custom-message-encoding.aspxWhen connecting to a web service sometimes you may get following exception or similar: &quot; Content Type text/xml; charset=utf-8 was not supported by service http://localhost:8000/calculator .&#160; The client and service bindings may be mismatchedenCommunityServer 2008 SP1 (Build: 30619.63)http://developers.de/blogs/damir_dobric/archive/2008/04/18/custom-message-encoding.aspx#13105Tue, 13 Jul 2010 15:59:12 GMT7e491611-45ad-4dae-a68f-c4cb64439510:13105Hassan Gulzar<p>I added the reference to the DLL but I&#39;m unable to use the extension. I get this error:</p> <p>The element &#39;binding&#39; has invalid child element &#39;daenetTextMessageEncoding&#39;. List of possible elements expected: &#39;context, binaryMessageEncoding, compositeDuplex, oneWay, httpTransport, httpsTransport, msmqIntegration, msmqTransport, mtomMessageEncoding, namedPipeTransport, peerTransport, pnrpPeerResolver, privacyNoticeAt, reliableSession, security, sslStreamSecurity, tcpTransport, textMessageEncoding, windowsStreamSecurity, transactionFlow, unrecognizedPolicyAssertions, useManagedPresentation, webMessageEncoding, discoveryClient, byteStreamMessageEncoding&#39;</p> <div style="clear:both;"></div><img src="http://developers.de/aggbug.aspx?PostID=13105" width="1" height="1">