So, the strategy files do not have trade initiation logic but there is a separate file that does, CrossoverStrategyBase.cs. Also no risk management part but there is BaseStopsAndTargetsStrategy.cs. I am guessing that there is a way to compile these with for example MaCrossover.cs and produce a working strategy with optimizable stops and targets.
I am thinking that these separate files are a technique to reuse code and compartmentalize logic. I am not a programmer.
Also, it is a mystery to me how when I compile my .dll, my tickblaze platform knows about it and the indicator or strategy is there ready to go to work. I am guessing that somehow my .dll gets incorporated into the main tickblaze .dll. Also guessing that the only one who can see the source for my indicator is me or anyone I give the source to.
Sean has mentioned sharing the code to some items, VMLean for example but I do not see that any where.
Anyway, I think that if I figure out how to put these files together in VS, I will not have any problem coding indicators and strategies, using the example files for my education.
It would be nice if there was a document explaining the available tickblase functions. I am guessing that perhaps because tickblase is in beta they might not be up for spending time on that because things might change?
I am putting this out here in case anyone else is traveling a similar path or even better already knows the answer for how to tell VS to put these files together.
I am pretty sure that I could just cut and paste them into one file but that would short circuit the engineering advantage that I assume is the reason for their separation.