You could switch to property imports and fix them up post-deserialization, but I'd be concerned about the fragility of mixing parts and serialization this way. As a rule of thumb, things with a 'persistent identity' make poor parts- MEF really wants to be in control of which instance is used where.
In this situation I usually try to separate the serialized and non-serialized data into different (related) classes. This might work for you..?
Good luck!
Nick
In this situation I usually try to separate the serialized and non-serialized data into different (related) classes. This might work for you..?
Good luck!
Nick