Topics
Replies
taras.alenin
02 Feb 2023, 07:10
( Updated at: 02 Feb 2023, 07:43 )
Thanks for your response. A follow up question. I currently have all my Indicators and Robot projects in their own directories. All sharing a common solution folder. What are you suggesting is the correct directory structure should be?
E.g. here the output of the build with 1.0.6. As you can see, the name is derived from the overall solution folder 'BigT' not the name of the directory of this particular indicator in this case 'BigT.FractalFarcture'.
1>BigT.FractalFracture -> C:\Users\Taras\source\repos\BigT\BigT.FractalFracture\bin\Debug\net6.0\BigT.FractalFracture.dll
1>BigT.FractalFracture -> C:\Users\Taras\source\repos\BigT\BigT.FractalFracture\bin\Debug\net6.0\BigT.algo
1>BigT.FractalFracture -> C:\Users\Taras\OneDrive\Documents\cAlgo\Sources\Indicators\BigT.algo
I appreciate you have reasons for the change. However, why take away the ability for the developer to control the name of the output *.algo file directly, explicitly. That way if one wants a solution structure in a way that makes sense to them, they can. I.e. can we please have the following option back.
<AlgoName Condition="'$(AlgoName)' == ''">$(MSBuildProjectName)</AlgoName>
Thanks,
Taras
@taras.alenin
taras.alenin
11 Feb 2023, 14:16
Differentiate by Instance ID
Hey Team,
Any more information about the "Differentiate by Instance ID"? What does it do, and how to use this?
Thanks!
@taras.alenin