WCF basic HTTP and NetTCP binding, exposing both via Mex?

If you have two MEX endpoints, each needs a separate address - call one "mex", then call the other "mex2" or something.

Thanks for the tips guys. It turns out the problem was with the baseAddress values pointing to "localhost". In the WSDL that's generated, it still says "localhost", so WSDL.

Exe is apparently trying to reach localhost (my dev machine) instead of the server. I changed the "localhost" to the actual IP of the server that hosts the service, and WSDL. Exe worked successfully, even in .

NET 1.1. And I can still get the 4.0 version by using svcutil.exe.

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.