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_BrandonH]

Hello jeronymite,

Thanks for your notes.

Our development and support have tested exporting with Agile 6.9.1.2 on NinjaTrader 8.1.3.0 and importing into 8.0.28.0 and 8.1.1.7 successfully. However, a few specific users are reporting an issue that may be isolated to specific computers and our development is investigating further into this.

Below is a link to a video of our testing to show everything should be fine exporting with the latest release and importing into previous releases.

https://drive.google.com/file/d/1uK_rbIFCmUMDDHovAWbs5vUw1suBn4DW/view

If you are planning to export with Agile on 8.1.3.0, please test importing on 8.0.28.0 and report back if this was successful.

We appreciate any information you can provide on this topic.

[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.

[NinjaTrader_BrandonH]

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.