Serialization revisited; and is there an alternative?

[Hyper]

Food for thought, and a couple of Challenge Categories

Challenge #1
Goal is to change an Indicator implementation, which
is provided by an Assembly DLL, without disrupting
the serialization/deserialization of the component
on a NinjaTrader chart restart. THIS SOLUTION REQUIRES
A RESTART of the NinjaTrader platform, but
the Indicator's implementation is altered through
a NEW Assembly DLL which functions as the
"plugin" for the Indicator's behavior. NinjaTrader would
not see any changes; and the Interface to
the Assembly would not change; and the
serialization/deserialization would be completely
unaffected by the change, on the restart, since a New
Assembly version DLL would have been
provided for the restart. And that plugin is
unknown to the NinjaTrader mechanisms, because
the MEF facility provides those linkages.

Challenge #2
Goal is to "Hotswap" an Indicator's plugin
Assembly DLL implementation
without having to restart the NinjaTrader
platform. Now that one's a real challenge !!
Can we do it with the MEF plugin approach?

hyperscalper

[NinjaTrader_ChelseaB]

Hello hyperscalper,

Would the methods in the dll have different signatures (overload parameters) or would these be the same?

Is the class or method name changing?

Are you referring to saving an indicator or strategy in a workspace and serializing inputs?