Get rid of tempuri in wsdl?

Question

Hello!
I have the problem that my WSDL file generated from my WCF service still contains a tempuri value although I did what the various forums say:

1. Put a [ServiceContractAttribute] into the declaring interface

[ServiceContract(Namespace = "www.XXX/Wcf")]
public interface ICaseService
{
[OperationContract]
ServiceGetCaseResponse GetCaseData (ServiceGetCaseRequest request);
}

2. Put a [ServiceBehaviorAttribute] into the implementing class

[ServiceBehavior(Name="CaseService", Namespace="www.XXX/Wcf")]
public class CaseService : ICaseService
{
public ServiceGetResponse GetCaseData(ServiceGetCaseRequest request)
   {
   // do some stuff here...
   }
}

3. Put a "bindingNamespace" attribute into the web.config
<services>
<service name="CaseService" behaviorConfiguration="CaseService.Service1Behavior">
        <endpoint address="http://127.0.0.1:9998/CaseService.svc"
                  binding="basicHttpBinding"
                  contract="HaWcfCoreServices.ICaseService"
                  bindingNamespace="www.XXX/Wcf"
                  bindingConfiguration="Binding_CaseService"
                  name="WCFEndPoint">
        </endpoint>


        <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/>

</service>
</services>

In my opinion all the facts for removing the tempuri should be given. There is no difference if I host with the Wcf-testhost or the IIS.

The WSDL-file:

<wsdl:definitions name="CaseService" targetNamespace="www.XXX/Wcf">
<wsdl:import namespace="http://tempuri.org/" location="http://127.0.0.1:9998/CaseService.svc?wsdl=wsdl0"/>
-
<wsdl:types>
-
<xsd:schema targetNamespace="www.XXX/Wcf/Imports">
........

http://127.0.0.1:9998/CaseService.svc?wsdl=wsdl0 in the browser tells me this:

<wsdl:definitions targetNamespace="http://tempuri.org/">
<wsdl:import namespace="www.XXX/Wcf" location="http://127.0.0.1:9998/CaseService.svc?wsdl"/>
<wsdl:types/>
.....

How can I get the tempuri.org removed?
Thank you for any idea!

Greetings,
Harry

Harry · Answer

Looks easy :-) Now I think I have the solution: In my implementing class I had to state this: [ServiceBehavior(Name=CaseService Namespace=www.XXX/Wcf/CaseService ConfigurationName = CaseService )] public class CaseService : ICaseService { ... } The name has to be the same as in the web.config: name=CaseService behaviorConfiguration=CaseService.Service1Behavior> binding=basicHttpBinding contract=ICaseService bindingNamespace=www.XXX/Wcf/CaseService bindingConfiguration=Binding_CaseService name=WCFEndPoint> the the tempuri is gone...???!!! I hope this will still work tomorrow! Thank you very much for your support! Harry

Jerry OBrien · Answer

Thanks a million Harry. Not only did your excellent follow-up ([ServiceBehavior(Namespace = Constants.ServiceNamespace ConfigurationName =  >) solve the problem of tempuri in my import namespace but it also let my wsHttp binding show up in the WSDL instead of defaulting to basicHttp which was really puzzling me.

John Penn · Answer

If I create a web service project in VS2010 (.Net 3.5) it generates the following stub code: namespace CSCorner1 { /// /// Summary description for Service1 /// [WebService(Namespace = http://tempuri.org/)] [WebServiceBinding(ConformsTo = WsiProfiles.BasicProfile1_1)] [System.ComponentModel.ToolboxItem(false)] // To allow this Web Service to be called from script using ASP.NET AJAX uncomment the following line. // [System.Web.Script.Services.ScriptService] public class Service1 : System.Web.Services.WebService { [WebMethod] public string HelloWorld() { return Hello World; } } } All I needed to do to remove the tempuri from the wsdl was change the WebService attribute.

Harry · Answer

Yes I guess I did not forget any reference - but I guess I must have forgotten something. Given following servies and classes: [ServiceContract(Name=CaseService Namespace = www.XXX/Wcf/CaseService)] public interface ICaseService { [OperationContract] ServiceGetCaseResponse GetCaseData (ServiceGetCaseRequest request); } implementing class [ServiceBehavior(Name=CaseService Namespace=www.XXX/Wcf/CaseService)] public class CaseService : ICaseService { public ServiceGetResponse GetCaseData(ServiceGetCaseRequest request) { // do some stuff here... } } web.config binding=basicHttpBinding contract=HaWcfCoreServices.ICaseService bindingNamespace=www.XXX/Wcf/CaseService bindingConfiguration=Binding_CaseService name=WCFEndPoint> Do I have to assign the same attribute values also to the request- and response-classes? e.g. [DataContract(Name=CaseService Namespace=www.XXX/Wcf/CaseService] public class ServiceGetCaseRequest : ServiceBaseRequest { ... } [DataContract(Name=CaseService Namespace=www.XXX/Wcf/CaseService] public class ServiceGetCaseResponse : ServiceBaseResponse { ... } What's with the base classes (ServiceBaseResponse ServiceBaseRequest)? Do they also have to have the [DataContract(Name=... Namespace)] attribute? I hardly can't remember a combination I did not try yet...do you have any idea more? Thank you very much! Harry

John Penn · Answer

Did you change all of the namespace references to specify CaseService? ServiceContract ServiceBehavior and bindingNamespace should all be the same and all should refer to CaseService.

Harry · Answer

Hello John just tried it but still the same result: tempuri. Do I just to need to adjust the namespace in the class or also in the interface and/or web.config. Think I alredy tried every possible combination :-( What if the service returns a class (e.g. ServiceGetCasesResponse.cs): what about its [DataContract(Namespace=...)] value? Kind regards Harry

John Penn · Answer

The namespaces have to match the name of the class: [ServiceBehavior(Name=CaseService Namespace=www.XXX/CaseService)]