BETA TEST Announcement (SidiFootprint)

[sidlercom80]

After several months of preparation, we would like to invite you to BETA test our new SidiFoodprint indicator. We have worked hard to bring you one of the best footprint indicators out there for NinjaTrader8.
For more information, please visit our discord channel : https://discord.gg/5TgsZJPcVM

[Teebone21]

I love your indicators but always have errors when installing or removing them

[sidlercom80]

I love your indicators but always have errors when installing or removing them

Hi Teebone21, I use a common dictionary for all my files. If I have to change something in this dictionary, I unfortunately have to recompile all the indicators. That this is often the case is because I work on different projects every day as an example, if you have already installed an indicator and want to install a new one, and it comes to problems, it is mandatory to also re-download and re-install the "old" indicator, so that the newly created library also adapts to the "old" indicator. If you know how to do it, it is not a big deal. The best thing is to come to our Discord server, there it is better described, how exactly to proceed, if problems with the installation should occur, or we can help you better there.

[NinjaTrader_ChelseaB]

Hello sidlercom80,

Ensure that all dependent classes are in a separate dll file.

https://drive.google.com/file/d/1D9qMVu1Ahb58Z82IVT0R7caTu0icg9nC/view?usp=sharing

So when you import, there are no duplicate class errors.

[sidlercom80]

Hi ChelseaB, thank you for your comment. Yes I know that, I do it that way ;-) Now if you change something in the "CommonIndicators.dll" file like in your example and recompile it, you have to recompile BOTH your "CustomStrategy1_Assembly.zip" and "CustomStrategy2_Assembly.zip" files. It is not enough if you're only one of both, e.g. the "CustomStrategy1_Assembly.zip" make new, because in the old "CustomStrategy2_Assembly.zip" folder is still the old "CommonIndicators.dll" in it.

[NinjaTrader_ChelseaB]

Hello sidlercom80,

As long as both hosting scripts that are already imported are referencing the same common dll, and that common dll needs to be changed, then both host scripts need to be updated anyway.

You could put both hosting script dlls in the same export along with the common dll, and it should update all 3 without any errors.

[sidlercom80]

We are still in the middle of the beta test for our new SidiFoodprint indicator, so if you want to participate, please contact us.

For more information, please visit our discord channel : https://discord.gg/5TgsZJPcVM

Soon there will be the next update with some new stuff