Export Error - asking for required components but nothing missing

[johnMoss]

Obviously there is but I don't know what... and FTR I'm using the latest NT8 (8.1.1.6)

1) Summary: I've taken my standard CS script [Indicator A] and as usual was successful in creating an export file which was tested and working fine several times over. It's resources included other proprietary indicators, and a few system indicators. All regular .cs files, and export just fine; downloadable and working check good on new computer.

2) In Export, I am now creating a compiled assembly for it, i.e. .dll .

3) All components of Indicator A were previously standard .cs assemblies. All but one needed file still remain standard .cs.
Only now however, one of these supporting indicators is now also converted to a .dll [Indicator B]

4) Indicator B as stated was a .cs, got converted as well, and is now is a .dll.

5) I recompiled Indicator A using Indicator B in its .dll format. Indicator A compiled successfully and proves check good on a chart. Log also shows no reported issues when on chart.

6) So currently Indicator A is still a .cs file, but now utilizing one .dll reference source (Indicator B).

7) I am now trying to export Indicator A as a compiled assembly, with the ONLY difference is that Indicator B is now a .dll

8) All other required components as needed previously are being included , with the sole exception that Indicator B is now pulled from the reference category.

9) The system is generating an error stating to be sure to include all necessary files and of course Export attempt fails. The Log reports no issue on this.

10) Am I missing some sort of system bridge file or something of that nature to reference the included .dll?

Thanx
JM

[johnMoss]

I should note also that previously the export engine did notice some proprietary indicators which utilize system indicators were not manually loaded into the attempt, and would do so automatically, i.e. "The following indicators will be...." on compilation execution. Does the presence of the referenced file now mean I have to ensure EVERYTHING is manually included in the added files sequence? (The now .dll file does not call any outside indicators)

[NinjaTrader_ChrisL]

Hello, thanks for writing in. I think the best way to solve this will be for me to log into your PC through TeamViewer. Please send an email to scriptingsupport at ninjatrader.com and reference "ATTN ChrisL" in the body of the email so we can chat in private about the code being used. I am available to log in Mon-Fri 7AM-4PM MST.

[johnMoss]

Email Sent

[NinjaTrader_ChrisL]

We have determined the cause of this issue to be the use of "borrowed" enums in the custom script. The script was referencing an enum from NetChangeDisplay to set up a user defined Draw.TextFixed location. The solution is to use our own Enums and create a condition for each possible enum value e.g.

if(MyEnumNamespace.MyEnum == MyEnum.TopLeft)
{
Draw.TextFixed(..., TextPosition.TopLeft, ...);
}

if(MyEnumNamespace.MyEnum == MyEnum.TopRight)
{
Draw.TextFixed(..., TextPosition.TopRight, ...);
}

Here is an example on how to create your own enum:

https://ninjatrader.com/support/helpGuides/nt8/NT%20HelpGuide%20English.html?creating_a_user-defined_parame.htm