First to answer your questions:
- I think the namespace get's important the moment you will split up the wsdl into separate files, but here is where my wsdl knowledge stops. This seems like a nice article about the importance: https://msdn.microsoft.com/en-us/library/aa480511.aspx. For this simple tutorial all definitions are in the wsdl so it does not matter.
- Yes the only file to deploy to the target should be HelloWorldWebService.exe. The wsdl, for this sample doesn't have to be on the target. The actual intention for the wsdl file (might be an interesting new blog post as well) is that a wsdl is on the target. That way 'any' client application can import the wsdl via the link pointing to the wsdl on the target and can write there application without the need of the physical wsdl file.
I am almost done finishing my blog post about running the sample for WEC7 and WEC2013. While testing everything seemed to work. When I only started the client application I got the error "Request failed: Could not find default endpoint element that references contract.......This might be because no configuration file was found!
It seems that next to HelloWebServiceClient.exe on the desktop, you also need HelloWebServiceClient.exe.config next to the executable....But is regarding the client application running locally on the desktop.
The blogpost will have my solutions as an attachment,
Stand-alone
First to answer your questions:
- I think the namespace get's important the moment you will split up the wsdl into separate files, but here is where my wsdl knowledge stops. This seems like a nice article about the importance: https://msdn.microsoft.com/en-us/library/aa480511.aspx. For this simple tutorial all definitions are in the wsdl so it does not matter.
- Yes the only file to deploy to the target should be HelloWorldWebService.exe. The wsdl, for this sample doesn't have to be on the target. The actual intention for the wsdl file (might be an interesting new blog post as well) is that a wsdl is on the target. That way 'any' client application can import the wsdl via the link pointing to the wsdl on the target and can write there application without the need of the physical wsdl file.
I am almost done finishing my blog post about running the sample for WEC7 and WEC2013. While testing everything seemed to work. When I only started the client application I got the error "Request failed: Could not find default endpoint element that references contract.......This might be because no configuration file was found!
It seems that next to HelloWebServiceClient.exe on the desktop, you also need HelloWebServiceClient.exe.config next to the executable....But is regarding the client application running locally on the desktop.
The blogpost will have my solutions as an attachment,