WCF contracts - namespaces and SerializationExceptions?

I'd say your third-party service is badly broken. There's a namespace collision here - there are two elements named response but with different XML Schema types.

I'd say your third-party service is badly broken. There's a namespace collision here - there are two elements named response but with different XML Schema types. I think you're going to have to not use any .

NET technology that involves deserializing this XML. There would be no way to tell . NET into which .

NET type to deserialize the XML. You'll just have to do it by hand. LINQ to XML is handy for this purpose.

– qntmfred Mar 12 '10 at 2:29 @qntmfred: It would have to assume that GetBar will never return a FooResponse. Given that it's easy enough for a service to return different elements for each response, I don't fault . NET for not making such an assumption.

– John Saunders Mar 12 '10 at 2:34.

You can try with response class like this: XmlRoot("response") public class Response { XmlElement("foo") public string Foo { get; set; } XmlElement("bar") public string Bar { get; set; } }.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.