NT Version (8.1.2.0) import error with a protected compiled assembly

[NinjaTrader_BrandonH]

Hello sidlercom80,

Thanks for your notes.

NinjaTrader_ChelseaB would like to schedule a remote support call with you so that he may investigate this matter further.

Please write in to scriptingsupport[at]ninjatrader[dot]com with a brief description of your inquiry, a phone number where you could be reached, and a good time to schedule a remote support call (with the time zone as well). Our regular support hours are 7am to 4pm CST, Monday through Friday.

In the subject of your email include 'Attn ChelseaB' and in the body of the email include a link to this forum thread.

[sidlercom80]

Hi all,

has anyone outside of NinjaTrader been able to export a protected assembly using 8.1.3.x and Agile.NET 6.9.1.2 and then import it successfully into both 8.1.1.7 and 8.0.28.0?
Anyone who has tried without success is also welcome to write. I would be interested to know if I'm the only one for whom it doesn't work

[jeronymite]

I come back to simple questions:

1. What is required to export from 8.1 to import into 8.1?
2. What is required to export from 8.0 to import into 8.0?
3. Given that both of the above are required, what is the official supported solution to achieve both of these on the same system?

This not a "nice to have" matter. Customers who remain on 8.0 must be supported. Customers who choose to migrate to 8.1 must be supported. Both need support via exports from both versions (8.0 and 8.1). This must be made possible on one system.

Whilst export between streams (8.0 to 8.1 and 8.1 to 8.0) may be desirable for some, the questions above are the minimum requirement for adequate vendor support of the product.

Still waiting for answers to these fundamental questions.

Thanks.

[sidlercom80]

Short update from me. Chelsea from NT support was also able to confirm my problem during a TeamViewer session and recorded everything and forwarded it to the development team. I'm now waiting for an answer. Unfortunately, another issue occurred to me in the meantime. Yesterday, I suddenly couldn't get any more data from the historical server, so the chart was only updated live. The new version 8.1.3.0 is therefore unusable for me, and I will downgrade again to the old 8.1.1.7 until there is perhaps a version that works properly.

[QuantKey_Bruce]

sidlercom80 During the testing session was there any indication this was a local issue or unique to you? Is there anything unusual about your installation?

[sidlercom80]

QuantKey_Bruce it was tested with a blank new NT 8.1.3.0 version for export and a blank new NT 8.0.28.0 version for import.

[QuantKey_Bruce]

sidlercom80 Was the specific failure that the assemblies created did not work on 8.1.1.7 or 8.0.28.0? And this was with the NinjaTrader Edition of Agile.NET 6.9.1.2?

[sidlercom80]

QuantKey_Bruce Take a look at my videos from post CAC40, IBEX35 intruments Best TWS version to use? #164, that explains your questions.

[jeronymite]

I come back to simple questions:

1. What is required to export from 8.1 to import into 8.1?
2. What is required to export from 8.0 to import into 8.0?
3. Given that both of the above are required, what is the official supported solution to achieve both of these on the same system?

This not a "nice to have" matter. Customers who remain on 8.0 must be supported. Customers who choose to migrate to 8.1 must be supported. Both need support via exports from both versions (8.0 and 8.1). This must be made possible on one system.

Whilst export between streams (8.0 to 8.1 and 8.1 to 8.0) may be desirable for some, the questions above are the minimum requirement for adequate vendor support of the product.

And still waiting for answers to these very fundamental questions. NinjaTrader Support?

Thanks.

[NinjaTrader_ChelseaB]

Hello jeronymite,

"What is required to export from 8.1 to import into 8.1?"

For NinjaTrader 8.1.2.1 using Agile, Agile 6.9.1.2 is needed for the export to import into 8.1.2.1. However, this version will eventually be unable to export with agile and an update to 8.1.3.0 will be required.
For NinjaTrader 8.1.1.7 using Agile, Agile 6.6.0.35 is needed for the export to import into 8.1.1.7 (or any other release).

"Given that both of the above are required, what is the official supported solution to achieve both of these on the same system"

NinjaTrader 8.1.3.0 using Agile 6.9.1.2 would be required to export on the same system and import into any of the previous releases.

Note, any other code breaking changes would still have an effect, such as the changes to Newtonsoft which would also prevent scripts referencing newtonsoft from the latest release from importing into older releases.


Our support and development has tested, successfully, exporting from 8.1.3.0 and importing into 8.1.1.7 and 8.0.28.0 and we are not running into any issues with this. Our teams are not able to reproduce this behavior using the SampleUniversalMovingAverage as the testing export script.

While we have had specific individuals state they are not import 8.1.3 scripts into 8.0.28, this looks to be isolated to specific machines. We have not been able to get a specific set of steps our development can use to reproduce. Reproducing is required for a fix.

[sidlercom80]

the only problem I personally see is exporting from 8.1.3.0 with Agile 6.9.1.2 (NT Edition) AND referencing Newtonsoft (13.*.*.*), this does NOT work in 8.1.1.7 or 8.0.28.0. this is what I have tested and can confirm.

[jeronymite]

Thanks, NinjaTrader_BrandonH and NinjaTrader_ChelseaB. I appreciate your responses. They help to clarify various scenarios.

Some additional comments/questions:

• Support for exporting from 8.0 is not mentioned in the explanations. This is a significant omission. Many users remain on 8.0 for a multitude of valid reasons.

• Returning to the original concerns then:
  • How is one to export from 8.0 to 8.0 and export from any 8.1 to any other version, both on the same system? (All code compatibility considerations are a given.)
  • If multiple different Agile versions are required, how can this be achieved on the same system, with no additional Agile licence costs?
  • Re-iterating that this is not a "nice to have". If vendors cannot support both 8.0 and 8.1 customers, this is highly problematic.

Thanks.

[QuantKey_Bruce]

Hello jeronymite,

Thanks for your notes.

To export protected assemblies from NT 8.0.28.0 or from NT 8.1.1.7 you would have to use Agile 6.6.0.35 to import into 8.0.28.0, 8.1.1.7, or any other release.

To export protected assemblies from NT 8.1.3.0 or from NT 8.1.2.1 you would have to use Agile 6.9.1.2. to import into 8.1.3.0, 8.1.2.1, or any other release.

Regarding 8.1.2.1, keep in mind the note from Chelsea on post # 177: "However, this version will eventually be unable to export with agile and an update to 8.1.3.0 will be required."

In our testing, we have successfully exported from NT 8.1.3.0 with Agile 6.9.1.2 and imported the assembly into 8.1.3.0, 8.1.2.1, 8.1.1.7, and 8.0.28.0, and we are not running into any issues with this. Our teams are not able to reproduce this behavior using the SampleUniversalMovingAverage as the testing export script.

Reproducing the behavior is required for a fix to be implemented and we have not been able to get a specific set of steps our development can use to reproduce.

NinjaTrader_BrandonH I have attempted to test this again here today on NT 8.1.3.1, and it does not appear to me to work at all.

Here's what I've done today by way of testing so far.

TLDR: Export from latest NT and Agile.NET from the help guide works on client systems without Agile.NET installed running NT 8.1.2.1 or 8.1.3.1 and does not work on NT 8.1.1.7 or 8.0.28.0.

Required files - NinjaTrader.Install.msi for 8.1.1.7 (saved from the previous release, since it was removed from the download page).

Part 1 - make a protected assembly using the latest authorized toolset

1. Clean Windows 11 machine, all windows updates up-to-date, just booted up.
2. Downloaded and installed NT 8.1.3.1 straight from account.ninjatrader.com download page.
3. Downloaded and installed Agile.NET 6.9.1.2 straight from the download link in the NT help guide under "Protection".
4. In NinjaScript Editor, opened up SMA and saved it as CustomSMA. No other changes.
5. Exported this indicator alone as a protected assembly CustomSMA.zip with a product name CustomSMA.
6. Set aside the exported protected assembly to the desktop.
7 Uninstalled NinjaTrader 8.1.3.1 and Agile.NET. Deleted the Documents -> NinjaTrader 8 folder. Deleted the Agile.Net license. Made sure there's no NinjaTrader 8 folder in Program Files or Program Files (x86) remaining (there wasn't).
7. Rebooted just to be sure everything is in a known way.

Part 2 - test the protected assembly on NT 8.0.28.0 without Agile.NET installed (FAIL)

1. Downloaded and installed NT 8.0.28.0 straight from account.ninjatrader.com download page.
2. NT 8.0.28.0 automatically installed with an @SIM license.
3. Connected to the automatically installed Kinetick EOD feed.
4. Opened a daily bar chart of @ES.
5. Imported the CustomSMA.zip file that was previously saved to the desktop. Noted there are no errors on Control Center's log tab. Imported successfully.
6. Attempted to put the CustomSMA indicator on a chart. This results in an error message popping up.


7. NinjaTrader at this point is hung, and had to be ended with task manager.
8. Uninstalled NinjaTrader 8.0.28.0. Deleted the Documents -> NinjaTrader 8 folder. Made sure there's no NinjaTrader 8 folder in Program Files or Program Files (x86) remaining (there wasn't).
9. Rebooted just to be sure everything is in a known way.

Part 3 - test the protected assembly on NT 8.1.1.7 without Agile.NET installed (FAIL)

1. Copied over and installed the previously saved NinjaTrader.Install.msi for version 8.1.1.7.
2. Logged in using normal account.ninjatrader.com credentials and selected Simulation.
3. Connected to the normal feed automatically.
4. Opened a daily bar chart of @ES.
5. Imported the CustomSMA.zip file that was previously saved to the desktop. Noted there are no errors on Control Center's log tab. Imported successfully.
6. Attempted to put the CustomSMA indicator on a chart. This results in an error message popping up.

7. NinjaTrader at this point is not hung, but CustomSMA is not in the indicator list. Unable to exit NinjaTrader because clicking on the X results in a hang. Ended with task manager.
8. Uninstalled NinjaTrader 8.1.1.7. Deleted the Documents -> NinjaTrader 8 folder. Made sure there's no NinjaTrader 8 folder in Program Files or Program Files (x86) remaining (there wasn't).
9. Rebooted just to be sure everything is in a known way.

Part 4 - test the protected assembly on NT 8.1.2.1 without Agile.NET installed (SUCCESS)

1. Downloaded and installed NT 8.1.2.1 straight from account.ninjatrader.com download page.
2. Logged in using normal account.ninjatrader.com credentials and selected Simulation.
3. Connected to the normal feed automatically.
4. Opened a daily bar chart of @ES.
5. Imported the CustomSMA.zip file that was previously saved to the desktop. Noted there are no errors on Control Center's log tab. Imported successfully.
6. Added CustomSMA to the chart. No error message in pop-up or on Control Center log tab. Indicator in list. Indicator runs normally (success).
7. Uninstalled NinjaTrader 8.1.2.1. Deleted the Documents -> NinjaTrader 8 folder. Made sure there's no NinjaTrader 8 folder in Program Files or Program Files (x86) remaining (there wasn't).
8. Rebooted just to be sure everything is in a known way.

Part 5 - test the protected assembly on NT 8.1.3.1 without Agile.NET installed (SUCCESS)

1. Downloaded and installed NT 8.1.3.1 straight from account.ninjatrader.com download page.
2. Logged in using normal account.ninjatrader.com credentials and selected Simulation.
3. Connected to the normal feed automatically.
4. Opened a daily bar chart of @ES.
5. Imported the CustomSMA.zip file that was previously saved to the desktop. Noted there are no errors on Control Center's log tab. Imported successfully.
6. Added CustomSMA to the chart. No error message in pop-up or on Control Center log tab. Indicator in list. Indicator runs normally (success).
7. Uninstalled NinjaTrader 8.1.3.1. Deleted the Documents -> NinjaTrader 8 folder. Made sure there's no NinjaTrader 8 folder in Program Files or Program Files (x86) remaining (there wasn't).
8. Rebooted just to be sure everything is in a known way.

What am I missing? Is there supposed to be a new Agile.NET that isn't documented in the help guide?

This does not appear to me to be fixed.

Also, NinjaTrader_BrandonH when you wrote, "To export protected assemblies from NT 8.1.3.0 or from NT 8.1.2.1 you would have to use Agile 6.9.1.2. to import into 8.1.3.0, 8.1.2.1, or any other release," when it comes to the "or any other release" part, did you actually run the indicators? Or did you just import them and it didn't give you an error message during import, so you assumed they were okay? It doesn't give the error message until you go to the Indicators list and try to configure one.

Please advise how we can move development work to the latest version and yet retain compatibility with NT 8.0.28.0 and NT 8.1.1.7. That does not appear to be how it is working.

Thank you.

Edit: added note that the Agile.NET version tested here was 6.9.1.2 exporting from NT 8.1.3.1.

[NinjaTrader_ChelseaB]

Hello QuantKey_Bruce,

To confirm, even without Agile applied, the export from 8.1.3.1 was not able to import and run in 8.1.1.7?

(This may indicate the issue is not an Agile issue and may be an issue with the computer or environment)

In testing, I am not able to reproduce. Which may indicate the issue may or may not be a bug with the platform but something specific to your computer.
Below is a link to the test.

https://drive.google.com/file/d/1KdrDlgXiqusrUMvmHogqH0Tm27Dp5vgf/view?usp=drivesdk

If you test the exact steps shown in the video, is the behavior different than what is shown in the video?


When you say "1. Clean Windows 11 machine, all windows updates up-to-date, just booted up." does this mean you deleted the Documents\NinjaTrader 8\ folder before re-installing NinjaTrader?
Or do you mean that you reformatted the hard drive and re-installed windows and this is the first time windows has booted?

Do you have a second computer you can use for testing to see if the issue is with the specific computer?

[QuantKey_Bruce]

Hello QuantKey_Bruce,

To confirm, even without Agile applied, the export from 8.1.3.1 was not able to import and run in 8.1.1.7?

(This may indicate the issue is not an Agile issue and may be an issue with the computer or environment)

No, I did not test importing a compiled assembly that was not a protected compiled assembly. I can do that, if you would like me to.

The computer was a clean Windows install. I can do it again, if it matters.

I will review your video to see if I can identify any differences in what we are doing.