Comments on ranamauro: WCF Service with Multiple Site Bindings: automatic...

the adresses ending in mex are for the mex endpoin...

2011-11-21T09:42:52.576-08:00

the adresses ending in mex are for the mex endpoint, that's just for that (Metadata EXchange). the intranet URI (http://svcserv/Services/ReportService/Reports.svc) should work just fine.

This is an example what I'm seeing: BaseAddre...

2011-09-20T13:08:47.628-07:00

This is an example what I'm seeing:

BaseAddress
{http://svcserv1.domain.com:818/Services/ReportService/Reports.svc}

ListenURIs
{http://svcserv1.domain.com:818/Services/ReportService/Reports.svc}
{http://svcserv/Services/ReportService/Reports.svc}
{http://svcserv1.domain.com:818/Services/ReportService/Reports.svc/mex}
{http://svcserv/Services/ReportService/Reports.svc/mex}

Going to the FQDN:port URL works fine, but if I go to the alias I receive a blank page. I'm assuming this is due to the single BaseAddress? Is it possible to respond to multiple URL entries?

The code looks great and I thank you for all your ...

2011-09-20T12:58:14.336-07:00

The code looks great and I thank you for all your hard work. Something seems off with my environment though. The return from CreateServiceHostCore() seems correct. In the debugger I can see there are 4 [service.Description.Endpoints] values but only a couple of the endpoints allow me to see the service when entering the URL into a web browser. The others simply give me a blank screen - no errors or anything to indicate success or failure. This is a step forward from the errors I was receiving, I suppose. ;)
Any ideas?