Operations
Exporting to NinjaTrader
The Export screen (a strategy's Export button, or sidebar → Export / Ctrl/Cmd+5) turns a discovered strategy into a complete, self-contained NinjaScript strategy class.
Generating the .cs
Under NinjaScript export:
- Class name (optional) — defaults to
Vsb_<spec hash>; anything you type is coerced to a valid C# identifier. The file is named after the class. - Include beta verification trace — optional diagnostics: the exported strategy writes a per-bar CSV while it runs in NinjaTrader, and the download includes the app engine's matching trace, so a NinjaTrader run can be compared bar-for-bar against the app's backtest. Turn it on when reporting a discrepancy during the beta — otherwise leave it off. (Matching engine traces exist for the validated top finalists of a run; if none exists for this strategy the app tells you.)
- Press Generate .cs — the exact source appears in a preview pane, along with an NT8 install guide and any warnings.
- Press Download to save the file (plus the trace CSV when enabled). The status line confirms where it was saved.
Heed the amber warnings box when it appears — it lists anything the export changed or can't reproduce (for example, experimental reversal exits flatten instead of reversing in the exported strategy).
What the generated code is
- Standalone. The class inherits NinjaTrader's own
Strategybase — no runtime, no DLLs, no dependencies beyond stock NinjaTrader 8. One.csfile is the whole strategy. - Readable. Entry trees and exits are lowered to plain NinjaScript you can open and audit.
- Deterministic. Re-exporting the same strategy produces a byte-identical file.
- Complete. The session-rule guardrails — daily limits, cooldowns, trade-hours windows — are carried into the code, so NinjaTrader behavior matches the backtest.
After the download
Continue to Installing in NinjaTrader. And before anything else, save the portable spec — Save spec… on the same screen — so the strategy can be re-evaluated on fresh data later.