Cannot import scripts into NT7.0!

[cassb]

When importing a compiled, protected NinjaScript file into a clean NT7 environment, I get an error message, which is attached. I have sent the zip import file to [email protected] and Kyle has experienced the same error. I don't know what the problem could be. Can you please help debug this?

Thank you!
Bryan

[NinjaTrader_Brett]

Hello,

Thank you for your forum post.

We are looking into this.

Thank you for your patience.

[NinjaTrader_Brett]

Hello,

Can you please upgrade to beta 21 and the recompile this and make sure it recompiles. There was some code breaking changes in beta 21:

Miscellaneous NinjaScript Information
– GetSessionDate() is no longer publicly exposed. Please use GetTradingDayFromLocal() instead.
– GetSessionBar() is now deprecated. Please use GetDayBar() instead.


Does this compile and export with Beta 21?

[cassb]

Hello,

Can you please upgrade to beta 21 and the recompile this and make sure it recompiles. There was some code breaking changes in beta 21:

Miscellaneous NinjaScript Information
– GetSessionDate() is no longer publicly exposed. Please use GetTradingDayFromLocal() instead.
– GetSessionBar() is now deprecated. Please use GetDayBar() instead.


Does this compile and export with Beta 21?

Yes it does. I'll send you another link to download it.

Bryan

[NinjaTrader_Brett]

Hello,

What ticket number did you get when you sent this in as I have not located it yet.

Thank You.

[cassb]

Hello,

What ticket number did you get when you sent this in as I have not located it yet.

Thank You.

Ticket 365230

[cassb]

Why was Kyle able to import the assembly without the eumerator problem, and you're having trouble now with the enumerators? Can we please have Kyle look at this case now? I would really like to fix the original issue that I posted above than to get distracted by enumerators.

Thanks!

[NinjaTrader_Kyle]

cassb,

To be clear, I was NOT able to import the assembly on the 9th of September as we were working over email.

[cassb]

cassb,

To be clear, I was NOT able to import the assembly on the 9th of September as we were working over email.

OK, thanks Kyle. I think Josh got it through my thick head what we needed. I did not realize that you can have just a bunch of "public enum ..." statements alone in a file, and that it would be included in the global namespace for all indicators to use. I thought I had to have the enum statements in their own namespace and then include that namespace in each indicator routine. Josh set me straight, so I think I'm all set for now.

Thanks for your help!