I am encountering a well documented issue in regards to instantiating a SoapHttpClientProtocol class. My situation is similar to the question posted here: http://stackoverflow.com/questions/172095/slow-soaphttpclientprotocol-constructor
A solution to the problem can be found here: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=87402
To summarize the article above, the problem has to do with the XmlIncludeAttribute's, which at runtime generates serialization code. The recommended solution, in the article referenced above, is to remove the XmlIncludeAttribute's and use a XmlSerializerAssemblyAttribute.
I have followed these directions (specifically Alternative 2) and they work great. However, if I were to run the same code in Mono (2.6), many errors occur (specifically in regards to Serialization).
If I include the XmlIncludeAttribute's (in Mono), however the instantiation of the SoapHttpClientProtocol class is slow (~25 seconds).
Is the XmlSerializerAssemblyAttribute supported in Mono? I have not been able to locate an article or post that suggests it is not supported.
In Summary: Removing the XmlIncludeAttribute from the generated code, including a XmlSerializerAssemblyAttribute and running in a .net environment, the instantiation of the SoapHttpClientProtocol class is acceptable, however it does not work at all in Mono. Any suggestions as to what can be done to ensure that the instantiation of a SoapHttpClientProtocol class is acceptable in a .Net environment as well as a Mono environment?