T
Tom
Recently I developed a .NET solution that supports a plug-in architecture.
Anyway, I load my plug-ins in a separate AppDomain like Microsoft suggest.
Anyway, I wanted to exchange data between two AppDomains using
AppDomain.GetData/SetData. This worked fine, except for XElement objects.
I'm assuming that XElement objects aren't marked with the [Serializable]
attribute (I didn't look with anything like ildasm).
Anyway, I got around this by passing strings back and forth and then
converting them back into XElement objects. I was just curious, is there a
reason why XElement objects aren't marked as serializable?
Thanks.
Anyway, I load my plug-ins in a separate AppDomain like Microsoft suggest.
Anyway, I wanted to exchange data between two AppDomains using
AppDomain.GetData/SetData. This worked fine, except for XElement objects.
I'm assuming that XElement objects aren't marked with the [Serializable]
attribute (I didn't look with anything like ildasm).
Anyway, I got around this by passing strings back and forth and then
converting them back into XElement objects. I was just curious, is there a
reason why XElement objects aren't marked as serializable?
Thanks.