|
| Hi Michael,
Thans a lot for your reply.
I am calling a .NET Component(Serialized) from Orchestration and passing
Messages to the component.The component initialize the message with an
xmldocument , modifies it and return as an xmldocument(Serialized) to the
Orchestration.The returned xmlDcoment is assigned to a message inside the
Orchestration.
Also I am using XmlDocument variables in my Orchestration to construct
messages and assign messages temporaly.Do I need to serialize the XmlDocument
variables used in the Orchestration ?
That means i need to convert all the XmlDocument variables in the
orchestration to Microsoft.XLANGs.RuntimeTypes.XmlSerializationProxy ?
Please advice me .Also if you can please provide me the details about where
i can find the detailed information on Serialization funda and using
XmlDocument inside Orchestration .I am bit confused with the concept behind
using xmlDocument with Orchestrations especially when calling .Net Components.
--
Many Thanks,
Sulaiman Abubacker
"Michael Elizarov [MSFT]" wrote:
> The reason is that XmlDocument is not serializable. All types that you use
> in an orchestration need to be binary serializable. The reason is that when
> send shape completes instance state is persisted, and this involves
> serializing. If you have any non-serializable objects in your code you will
> fail.
>
> -- Michael
>
> --------------------
> a
> code
> tMessage></InputMessage></ns0:Error>");
> to
> Version=1.0.5000.0,
>
>
|
|