changing asp .net web service namespace when already in productive state
- by eloQ
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…