I have generated a SVC proxy client using following switches:
svcutil /wrapped /serializable /async /seralizer:XmlSerializer /out:Proxy1.cs http://url.zzz/name.wsdl
so far so good,I call methods, get response all fine.
A step further, I read about xmlSerializers here http://msdn.microsoft.com/en-us/library/aa751883.aspx and managed to generate one serialization assembly for Proxy1.cs (converted to dll also).
Followed naming convention of dll and added reference to both dll in a test console application, fine, works ok. (Although I didn't notice anything in performance, not even a slight placebo).
Tried another way to use xmlSerializer, generated serialization code into a separate assembly and used the XmlSerializerAssemblyAttribute on the service contract that uses the XmlSerializerFormatAttribute(I placed it everywhere I could see it's needed while digging in, just for test) & set the AssemblyName to point to the compiled serialization assembly.
Again, works fine but I don't notice any change in performance.
Why is it so? Am I doing something wrong? or I need to test it on more complicated responses. Are there more ways to verify this? Is it really needed to generate Xmlserializer for perofrmance reason?
Thank you. I am a newbie here, please also share your experience. I am not only looking for a to the point answer but some pointers are also appropriated.