I see your point but the fact that you do lose the RADness is actually not a beneficial thing IMO. I do have a "Messages.dll" containing the web service types and I basically let wsdl generate the proxies of those types that are exposed via the webmethods. That way it's automatic. The types in my "messages.dll" use the "contract first" (or hybrid of contract first as I don't hand code a wsdl file too) development style. Meaning, I use xsd.exe to generate classes off of a message schema I define first. This is a very often the suggested web service dev strategy.
The issue that's confusing me is that for a test harness usage I'd like to be able to deserialize an xml string into a type so that I can use it as input to a web method parameter. When I attempt to this with the proxy class's schema, nothing in the serializer chokes but for some reason I don't get all internal classes populated from the deserialized string. Just the outer/containing class. However, if I do the same operation against the original, non-proxy type this object creation technique works great. Obviously something is being lost in the translation. It's not that I need to this to work per se it's just a lot easier to populate a large, complex object in one shot from deserialization instead of assigning everthing by hand. =================================== This list is hosted by DevelopMentor� http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
