It’s a long explanation, so I appended my answer to the post above. The short version is: I took the XmlElement route because I could change fewer lines of code. I didn’t have to create a new WebContentTypeMapper-derived class and figure out where to plug it in.

What do you think? An ugly hack?
Dean

I’m running into this same error and am wondering why you went the XmlElement way instead of getting WCF to treat the request as Raw?

By the way, did this error come about if you only had one WebInvoke on the service, or only after you added multiple WebInvokes?

Thanks,
Brad