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

Question

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

I tried to add a reference for the service from a Windows Form client built on .NET 2.0. I could get the Web

Answer 1

Your config doesn't quite line up.....

If you take all this into account, you get http://localhost:8002/HBAccess/ from the base address, plus mex from the MEX endpoint --> http://localhost:8002/HBAccess/mex

But in your behavior configuration, you use a different address for MEX:

Here, you point at http://localhost:8002/HBAccess/help/mex - note the extra /help in there. Now which one is it really??

I would recommend tossing away the explicit httpGetUrl in the service behavior config - just use:

and you should be able to get your MEX at http://localhost:8002/HBAccess/mex.

Marc