Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a 3rd party struct “XlOper” which is not marked with [Serializable]. I want to copy it to another AppDomain. What’s the best way to do this? Can I add an implicit custom serializer to a 3rd party class, or do I have to create an XlOperSerialized and use it explicitly on both sides of the domain boundry?
If it was me, yes I would just create a separate DTO model that I use on the boundary. It is usually trivial to do, insulates the boundary from implementation changes and versioning issues, and will work well in all such scenarios, regardless of whether remoting, WCF, SOAP or just a wrapped cross-AppDomain call. It will also give you more control over what is serialized (events being a problem, etc).