WCF Web Service chnage wsdl name and targetNamespace?

Add this to your service contract ServiceContract(Namespace = "some.com/service/"" rel="nofollow">some.com/service/", Name = "ServiceName" Add this to your service implementation ServiceBehavior(Namespace = "some.com/service/"" rel="nofollow">some.com/service/") Add this to your web. Config endpoint binding="basicHttpBinding" bindingNamespace="myservice.com.

Add this to your service contract ServiceContract(Namespace = "some.com/service/"" rel="nofollow">some.com/service/", Name = "ServiceName" Add this to your service implementation ServiceBehavior(Namespace = "some.com/service/"" rel="nofollow">some.com/service/") Add this to your web. Config.

I already have: ServiceContract( Name = "XXXXServices", Namespace = "schemas/XXXX/2010/03") public interface IPublicServices Doesn't make any difference when I generate the WSDL from the page listed in my original post. The above interface is implemented by a class called SearchServices, hence the name generated in the WSDL definiton when I click on the localhost:53456/ServicesHost. Svc?

Wsdl link – Graham Apr 1 '10 at 14:52.

Actually, it should be put on ServiceBehavior: ServiceBehavior(Namespace = "some.com/service/", Name = "ServiceName" Then WSDL name will be changed.

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.