and of course it is implemented as an assembly DLL since it has several
dozen classes.
Elsewhere on this forum, when I was starting out, implementing a Strategy
subclass; to be attached to a chart; I suffered through the discussion on
"clones" and just which one of the clones was to "survive" and become the
fully elaborated Strategy instance.
I solved that problem, not without a lot of issues; and have been using
this unmanaged Strategy for a while now.
However, for not much reason I can determine, the Chart to which the
Strategy is attached; decides that it is going to alter or perhaps reset, or
perhaps simply send a Terminate State to the Strategy instance...
...thus making this quite an unreliable method for me to use.
Enter the role of the AddOn. So, I was able to compile the excellent
AddOn example given; and I'm just going to have to re-implement my
Strategy code, no longer as a Strategy sub-class, but as an AddOn.
I'd be interested to know of others who have attempted to implement
complex Strategies as assembly DLL's (unmanaged) and have had
success in getting run-time stability. Because I simply can't make it
stable enough to eventually become a long-running Bot, for example.
Now, implementing as an AddOn is, of course, possible; but the "support
inheritance" of the Strategy base class is absent; and so quite a few
things need to be different, including Order Entry, etc...
But that's not a problem at all. What I'm looking for is long-running stability;
and so I'll just add to this thread some of the key milestones and challenges
I encounter as I re-implement my Strategy as an AddOn.
hyperscalper
Comment