Common AddOn in different binaries

[waldoalvarez]

Hello Everyone:

I have a question regarding a common addon used by several indicators. This addon is required by those indicators. My doubt is what would happen if I produce two binaries (one for each indicator) each having this required AddOn in the dll.

Would there be conflicts as both indicators have a copy of this AddOn? Both would use one of the copies? Each indicator will use it's respective copy (I am considering here different versions installed and possible conflicts users could experience).

Please document this a little.

[NinjaTrader_Jim]

Hello waldoalvarez,

Thanks for your post.

If both indicator exports include the same AddOn DLL, NinjaTrader will prompt the user if they want to overwrite the existing DLL. In this case, there would not be conflicts. Including the same AddOn/NinjaScript in separate DLL's can cause a conflict.

We suggest placing dependent/common NinjaScripts in their own DLL to avoid conflicts and versioning issues. You can then add a reference for the dependent DLL when you export your main DLL packages. (See screenshot attached.)

I have also attached some exports that describe how this would be setup. There are two SampleMACrossover strategy exports that use a custom "SMA2" indicator that is included as a separate DLL since it is dependency.

We look forward to assisting.

[waldoalvarez]

Thanks for clarification!