Can someone please help me understand how .Net handles replacing components, specifically web services...
I have a web service that is currently in production. I now need to add a new parameter to the function. I found out that you can't overload the function in a web service, so in my test environment, I just added the new parameter, and expected that my test client would break. It didn't break, so I figured that the old web service component must be in memory somewhere. I rebooted my test server, and again expected the test client to fail because it wasn't sending the new parameter. Again it didn't fail. To make a long story short, when I change the parameters (even when I add the new one in the middle of the param list), everything still keeps using the old version until they import the new wsdl file. If I change the function name however, then everything using the service breaks. That is why I am confused If a copy is stored somewhere, then why would it break when I change the function name? I guess what I am really trying to figure out is if I add the new parameter to the existing function, will the old clients eventually break, or will they continue to use the old code until they update their wsdl. Would I be better off just creating a new function with a new name? I would like to avoid changing the name of the function if possible, especially if I have to keep changing the name every time I change the signature of the function. Thanks, Shawn Brown =================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
