Thanks for pointing out these systems.
I guess the real question is about circular reference. It seems not able to put the base classes to a different assembly because of this.
Imagine some common functionalities that can be used by different strategies, there won't be one place to override and applies to all different strategies.
Multiple system under one "meta" strategy seems to be a way, but it needs all strategies residing in one assembly. Is there a way to create different assembly for different strategies, while still refering to the same base class?
Strategy 1 : StrategyBase
Strategy 2 : StrategyBase
Tuesday May 07 2013 by