Is basicHttpBinding really required when exposing a WCF service as a Web Service for .NET 2.0 Target Client? -

I have a WCF service and I am hosting it in Windows service.

I reference the service from a Windows Forms client built on .NET 2.0. I can get web context by pointing to httpGetUrl = "http: // localhost: 8002 / HBAccess / help / mex", but when I check Reference.cs - there is only one namespace in which there is nothing .

Now I add the original HTPP binding and repeat the same steps:

And now I can see the classes for web service.

My senior colleague says that httpGetEnabled will be sufficient enough to export the WCF service via http and create a proper web reference.

Does anyone tell me what am I missing?

  & lt; System.serviceModel & gt; & Lt; Services & gt; & Lt; Service transaction support = "HBAcsNX.HBAccessBehavior" name = "HBAcsNX.HBAccess" & gt; & Lt ;! - & lt; Endpoint address = "" binding = "basic HttpBinding" contract = "HBAcsNX.HBAccess" /> - & gt; & Lt; Endpoint address = "HBAccess" binding = "net TCPbinding" contract = "HBACNX.HABACC" /> & Lt; Endpoint address = "Max" binding = "MaxHttpending" contract = "IMAXADEXXchange" /> & Lt; Host & gt; & Lt; BaseAddresses & gt; & Lt; BaseAddress = "net.tcp: // add localhost: 18264 / habfus /" /> & Lt; BaseAddress = "http: // localhost: 8002 / habccc /" / / gt; Add & lt; / BaseAddresses & gt; & Lt; / Host & gt; & Lt; / Services & gt; & Lt; / Services & gt; & Lt; Behavior & gt; & Lt; ServiceBehaviors & gt; & Lt; Behavior name = "HBAcsNX.HBAccessBehavior" & gt; & Lt; ServiceDiBug includes ExceptionDetailInFaults = "True" httpHelpPageUrl = "http: // localhost: 8002 / HBAccess / Help" /> & Lt; ServiceMetadata httpGetEnabled = "true" httpGetUrl = "http: // localhost: 8002 / hbaf / support / mac" /> & Lt; / Behavior & gt; & Lt; / ServiceBehaviors & gt; & Lt; / Behavior & gt; & Lt; /system.serviceModel>  

// Result reference cs (blank proxy stub with namespace only)

  Disable #pragma warning 1591 namespace form. Service client {} #pragma Warning Restore 15 9 1  

issue Max Httbinding Your service is not really exposed, it only exposes an defenceition of your service, and because ..net 2.0 does not understand the nettap, , So you need basic HTML because this is actually your service end point.

If you look at the contracts you see, then there is no contract for Max HTPBinding "HBAcsNX.HBAccess" rather "iamatadataexchange".