Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
I was away for the last few hours, but @rleplae has said what I would have said anyway, I would only add the following things:
a) Ninja always compiles all indicator/strategy code modules every time, not just any that are touched or edited, worth knowing in any case.
b) References to external .DLL files are added or deleted using the right-mouse menu 'References' when in any file in the Ninja code editor and then compiling; they are system global so any file is fine to use. Check these just in case you can sort the mess easily this way.
c) However, In this case it looks like your main folders have been corrupted, either intentionally or accidentally by a process of installing or uninstalling that has gone awry. Some third party add-ons are not good in these areas, it is also easy to slip up as a user. It may not be easy to clean it up, and might well be easier to just rename the Documents/NinjaTrader folder to a different name and re-install Ninja. That will create a fresh install that you can then add/copy/import into what you really need, e.g. workspaces/templates/indicators/etc, thereby building a clean base one step at a time.
d) I keep a daily backup of the Documents/Ninjatrader folder to cover for just this sort of worst-case scenario. This can be a zip archive or a direct folder copy, disks are cheap enough these days. The Ninja built-in backup is far too slow for this, imho.
@ratfink, option b worked. I deleted a couple of the most recent assemblies (some time ago) that I know I'll never use, closed Ninja, and rebooted. The NinjaScript errors are gone! Thank you very much. Finally, something went in my favor.
