Bug with import/export limit

[frslvr]

Hello,
I stumbled upon a limitation of number of DLLs I can import
Here are the steps:
1. Create 7 primitive (empty) indicators with the indicator wizard
2. Export each of them as a dll
3. Delete or hide their .cs files
4. Import just one of the dlls
3. Create a primitive strategy with strategy wizard. Add a call of the indicator we just imported.
4. Export the strategy. It should work fine
5. Import the rest of our dlls
6. Try to export the strategy. It won't work now
7. Try to add the first dll as a reference won't help

[NinjaTrader_ChelseaB]

Hello frslvr,

I see you are posting in the Strategy Development section of the forums.

To confirm, are you trying to automate importing scripts using a strategy?

There are many users with far more than even 50 dlls imported without any issues.
Try testing each dll one by one, is there a specific dll that causes the behavior.

Where you have stated:
"3. Delete or hide their .cs files"

This will likely break NinjaTrader and cause compile errors. Don't do this.

To remove a third party assembly package:

• Click Tools -> Remove NinjaScript Assembly...
• Select the assembly to remove -> click the Remove button
• https://ninjatrader.com/support/help...emovingAdd-Ons

[frslvr]

Hi Chelsea,
Thank you for your quick reply.
I have developed strategies for NT for many years.
I just got this problem only when I reached 7 DLLs. They aren't specific.
Please try to follow the steps

[frslvr]

Here is the video: https://youtu.be/j_G9IdbgaMg

[NinjaTrader_ChelseaB]

Hello frslvr,

After exporting an open source script as a dll, remove the original script or exclude this from compiliation.

When exporting the host script that references the dll add the reference when exporting, then drag the dll into the .zip export file.

Below is a link to a video.

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

[frslvr]

As you can see in the video and as I mentioned in the steps:
3. Delete or hide their .cs files;
7. Try to add the first dll as a reference won't help

This is not the point. The point is that it has a limit to the number of imported assemblies.
Can you please repeat the steps I showed in the video?

[NinjaTrader_ChelseaB]

Hello frslvr,

Thank you for your patience and for the follow up.

During testing I was able to reproduce the behavior and I have reported this to our development team to investigate.