changing asp .net web service namespace when already in productive state
Posted
by eloQ
on Stack Overflow
See other posts from Stack Overflow
or by eloQ
Published on 2010-05-21T16:37:38Z
Indexed on
2010/05/21
16:40 UTC
Read the original article
Hit count: 244
by some unfortunate events we published a web service with the tempuri-namespace a couple of months ago and no one did notice (not in our company, not the companies connecting to the web service) even though it's live since that time and lots of companies (~25 i guess) already access this web service.
now i'm thinking of correcting that mistake and have the namespace fixed to a proper value.
the only problem is: as soon as we would do it, all the programs and services connected to this web service would stop working. i can't really allow that to happen.
is there any way to fix the namespace for future purpose or to have the web service operate under two namespaces as one web service?
any tip at all what i could do to get rid of the tempuri-namespace and have it fixed without needing to synchronize the change with all the external companies?
i'm all out of ideas, so any help would be much appreciated! thanks!
I hope this question is alright here, first time user, found this through using search engines on my research and found tempuri.org related posts, just not the right one..
© Stack Overflow or respective owner