{"id":8,"date":"2015-06-28T15:10:00","date_gmt":"2015-06-28T15:10:00","guid":{"rendered":""},"modified":"2016-01-30T22:39:54","modified_gmt":"2016-01-30T22:39:54","slug":"wcf-exposing-metadata-over-tcp","status":"publish","type":"post","link":"https:\/\/tpodolak.com\/blog\/2015\/06\/28\/wcf-exposing-metadata-over-tcp\/","title":{"rendered":"WCF – exposing metadata over TCP"},"content":{"rendered":"

I think that everyone who has ever been working with WCF<\/i> knows that we can enable metadata exchange by adding ServiceMetadataBehavior<\/i> to App.config<\/i> file<\/p>\n

\r\n\r\n     \r\n       \r\n         <\/serviceMetadata>\r\n       <\/behavior>\r\n     <\/serviceBehaviors>\r\n<\/behaviors>\r\n<\/pre>\n
Up until yesterday the build in solution works fine for me. However recently I’ve had to expose metadata over TCP<\/i> protocol. ServiceMetadataBehavior<\/i> doesn’t have something like TcpGetEnabled<\/i> property so in order to expose metadata over other protocols (in my case TCP<\/i>) it is necessary to add custom MEX<\/i> endpoint.<\/p>\n
\r\n\r\n    \r\n          \r\n            \r\n    \r\n            \r\n              \r\n                <\/add>\r\n              <\/baseAddresses>\r\n            <\/host>\r\n          <\/endpoint>\r\n        <\/service>\r\n    <\/services> \r\n    \r\n<\/system.serviceModel>\r\n<\/pre>\n
The endpoint configuration has to have a specific binding – in my case mexTcpBinding<\/i> (there are of course MEX<\/i> bindings available for other protocols). What is more, the contract has to be set to IMetadataExchange<\/i>. The address value is up to us, we can use full blown address as well as leverage base address. At this point if we run service we will get the exception
\n\"Exception\"<\/a>
\nEven though we added custom endpoint for metadata exchange we still have to use ServiceMetadataBehavior<\/i>. This time however we can skip httpGetEnabled<\/i> property<\/p>\n
\r\n\r\n\r\n        \r\n          <\/serviceMetadata>\r\n        <\/behavior>\r\n<\/serviceBehaviors>\r\n\r\n<\/pre>\n
I think that everyone who has ever been working with WCF knows that we can enable metadata exchange by adding ServiceMetadataBehavior to App.config file Up until yesterday the build in solution works fine for me. However recently I’ve had to expose metadata over TCP protocol. ServiceMetadataBehavior doesn’t have something like TcpGetEnabled property so in order […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,12],"tags":[159,167],"class_list":["post-8","post","type-post","status-publish","format-standard","hentry","category-c","category-wcf","tag-c","tag-wcf"],"_links":{"self":[{"href":"https:\/\/tpodolak.com\/blog\/wp-json\/wp\/v2\/posts\/8","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tpodolak.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tpodolak.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tpodolak.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/tpodolak.com\/blog\/wp-json\/wp\/v2\/comments?post=8"}],"version-history":[{"count":8,"href":"https:\/\/tpodolak.com\/blog\/wp-json\/wp\/v2\/posts\/8\/revisions"}],"predecessor-version":[{"id":522,"href":"https:\/\/tpodolak.com\/blog\/wp-json\/wp\/v2\/posts\/8\/revisions\/522"}],"wp:attachment":[{"href":"https:\/\/tpodolak.com\/blog\/wp-json\/wp\/v2\/media?parent=8"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tpodolak.com\/blog\/wp-json\/wp\/v2\/categories?post=8"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tpodolak.com\/blog\/wp-json\/wp\/v2\/tags?post=8"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
From now on we can access metadata over TCP<\/i>
\n\"metadata<\/a>
\nSource code for this post can be found here<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"