All about WSDL vs MEX?

It can be empty, i.e. , but it must be present. The service definition needs to reference the service behaviorConfiguration.

Check out the following for examples: request-response.com/blog/PermaLink,guid....

Check out serviceMetadata for more information regarding the WCF configuration file. To answer your questions though, MEX is a newer W3C standard for the presentation of Service description information, WSDL was the previous method. If you need to allow older clients to access your service description information, you may have to expose that information via WSDL.

The information for exposing your service description information as WSDL (httpGetEnabled) is also in the link provided above. Also, try using the wcftestclient. Exe to access your WCF service.It provides more functionality and information that a browser.

If you look at that endpoint, you'll see it looks like every other endpoint. There's even a service contract (IMetadataExchange). You can look at System.ServiceModel.Description.

IMetadataExchange and see what that contract is all about.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.