I bought Expert Service Oriented Architecture by Jeffrey Hasan the other day and I have only had a quick scan through it but it does have a lot of information on contract first web service development so you might find it useful.
As far as deserializing, I've been doing exactly what you're trying here without any problems. Make sure you pass the targetNamespace of your schema to the XmlSerializer constructor though. On 5/17/05, Bill Bassler <[EMAIL PROTECTED]> wrote: > I'm confused. > In a regular .net library app, I can generate a set of .net classes from a > schema using xsd.exe /c. I can then generate/deserialize to a fully > populated object based on the submitted xml doc string using: > > XmlSerializer serializerIn = new XmlSerializer(typeof > (Esylvan.EnterpriseLibrary.Types.ElmsEnrollment.ElmsResponse)); > System.IO.StringReader reader = new System.IO.StringReader > (_xmlResponseDocument.OuterXml); <-- xml doc string > _enrollmentResponse = > (Esylvan.EnterpriseLibrary.Types.ElmsEnrollment.ElmsResponse) > serializerIn.Deserialize(reader); > > However, if attempt basically the same deserialization process using a wsdl > generated proxy for that type deserialization "works" but the process does > not create any objects internal to the outer container as it does when I > deserialize directly from the xsd generated classes. > > Why? > I took a look at the xmlSerialization attributes and many (but not all) > between the proxy and the xsd generated classes are the same. > > =================================== > This list is hosted by DevelopMentor(r) http://www.develop.com > > View archives and manage your subscription(s) at http://discuss.develop.com > -- Regards, William D. Bartholomew http://blog.bartholomew.id.au/ =================================== This list is hosted by DevelopMentor� http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
