tag:blogger.com,1999:blog-8389214606941174691.post1133881179638295877..comments2024-03-23T02:47:30.648-07:00Comments on Tech Talk: How to get rid of http://tempuri.org/ in WCF WSDLelLocohttp://www.blogger.com/profile/04685538094487060639noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-8389214606941174691.post-15085392372834105742013-10-30T01:20:41.576-07:002013-10-30T01:20:41.576-07:00No the namespace in the web service uri can be bas...No the namespace in the web service uri can be basically anything. I has the exact same purpose as the namespace in c#,c++ or the package in java. You would not like to have a big code base in a single namespace and with web services that is the same.<br />The reason why it is often the url of the website is because the url of the website has to be unique by definition. And what is unique makes a good name space.elLocohttps://www.blogger.com/profile/04685538094487060639noreply@blogger.comtag:blogger.com,1999:blog-8389214606941174691.post-27871477512831175372013-10-29T15:43:33.052-07:002013-10-29T15:43:33.052-07:00Does it actually matter what the value of the name...Does it actually matter what the value of the namespace uri is ? I though it has to be the address of the web service like http://myserver.domain/mywebservice<br />or it does not matter ? If you have only one web service do you actually need to change the targetNamespace ?<br />Does the namespace uri have to reflect the location of the web service?<br />If the namespace has to reflect the location of the web service which will change depending on the server it is running on. In this case how can we change namespace in attributes without touching the code ?<br />Karolhttps://www.blogger.com/profile/06870289981257274294noreply@blogger.comtag:blogger.com,1999:blog-8389214606941174691.post-42824026504834498322013-07-12T02:00:43.792-07:002013-07-12T02:00:43.792-07:00Excellent tips... solved my problemExcellent tips... solved my problemAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-8389214606941174691.post-60468450407015559712012-06-11T10:21:12.964-07:002012-06-11T10:21:12.964-07:00bindingNamespace="http://myservice.com"
...bindingNamespace="http://myservice.com"<br /><br />I hope this not required in WCF4arunhttps://www.blogger.com/profile/10385530457290123476noreply@blogger.comtag:blogger.com,1999:blog-8389214606941174691.post-76727870858845938472010-03-18T10:08:25.490-07:002010-03-18T10:08:25.490-07:00Thanks for this but WTF?! Why no less than three ...Thanks for this but WTF?! Why no less than three places? the uber configurable WCF strikes again.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8389214606941174691.post-79637071915196729222010-01-19T07:08:06.245-08:002010-01-19T07:08:06.245-08:00Thanks from me too regarding 3rd point :)Thanks from me too regarding 3rd point :)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8389214606941174691.post-39405805497516665982009-11-18T23:11:15.644-08:002009-11-18T23:11:15.644-08:00Thank you! I had missed the endpoint BindingNames...<b>Thank you!</b> I had missed the endpoint BindingNamespace and this was driving my <i>nuts</i>!!Mikehttps://www.blogger.com/profile/07651046614904006739noreply@blogger.com