WCF Metadata publishing customization
Hello there, I have two questions some may find quite easy to answer.
My service has several end-points (like http, net.tcp & net.pipe). When I try to read default WSDL provided by WCF (likehttp://mycomputer/myservice?wsdl), I get description of all endpoints in published WSDL.
Is it possible to hide/remove non-http endpoints from WSDL?
I mean, what is a deep reason to publish net.tcp & net.pipe endpoints via HTTP one?
Second question, regarding default web-service http page, provided by WCF for wsHttpBinding.
Like "You have created a service blah-blah, use svcutil.exe <address> to generate proxy, C# demo, VB demo".
Is it possible to customize this page? Is it possible to have something like in ASPX, http test page where user can enter some parameters and actually trigger webservice methods?
Hi Alexey,
1) you can implement an IWsdlExportExtension and, by using the ExportEndpoint, change the wsdl. See this post on my italian blog (http://www.dotnetside.org/blogs/fabio/archive/2006/11/26/Turn-off-WS_2D00_Policy-in-WCF-_2E002E002E00_.aspx) The code is language-neutral 
2) I don't known if it is possible. I'm not sure, but you can implement your own HttpModule and modify the resulting page.
HTH
bye
<quote>There are no magic knobs to make, e.g. the test page like in ASPX, you'd have to build that feature on your own.</quote>
AFAIK, there is no built-in HTTP-GET/POST WebServices invokation as well.
Doesn't this mean, that WCF is downgrade of ASPX? People & software got used to these features, now comes new generation API (aka WCF) and some features are missing.
Help me find reasons to explain to my clients why WCF is better than ASPX and they better upgrade?
There are indeed some features in ASPX that are not in WCF. But there are many many more new features in WCF (e.g. just read any overview docs like
http://msdn2.microsoft.com/en-us/library/ms731082.aspx that talk about lots of WS/SOAP interop protocols, uniform programming model for talking over diverse transports, ...). If the get/post help page is a very important feature to the customer, then maybe they ought not upgrade, but there are lots of potentially good reasons to upgrade, just read our docs/press.
