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)
NinjaTrader and DLL's (creating and loading how-to)
You have already stated most of the risk, make sure you know who make the DLL and what their intension is with the program. If you just download random DLLs, you are at risk. futures.io (formerly BMT) generally doesn't allow DLLs for download except in rare circumstance because of the safety/security issues.
It is possible any DLL can steal any information from your computer, network, bank, trades, install a key logger, steal passwords, or anything else. You wouldn't know it if you can't view the source code.
@supermht, all the above responses are correct. I would just add that either most or all commercial indicators will come in the form of dll files, as will some non-commercial ones. The reason is that the creator of the indicator does not want you -- or any competitor! -- to be able to read his original source code, and see just what the indicator does and so be able to copy it.
This puts you in the bind of having to trust the original author, and his or her motivations. It does not mean the dll's are inherently dangerous, just that you cannot know if they are or if they are not.
So, if you are going to buy an indicator, you are probably going to get a dll. You will need to decide whether the provider of the indicator is trustworthy, which you have to do every time you install any software on your computer anyway (essentially all commercial software will come as either exe or dll files, neither of which show the source code). You will need to be very careful who you trust if you are downloading indicators.
You will almost never see a dll allowed on futures.io (formerly BMT), which is about sharing, not hiding.
when a program (exe) is running, or when a library (dll) is loaded in memory, you will not be able to compile and overwrite the file (exe/dll), visual studio will give you a error it can not output to the locked file.
when you recompile a dll, make sure you unload the old version and reload the new version, it's a good habit to put a version number in your DLL, increment that number every time you modify and recompile, and output that to your output window, that way you can be sure the right version is loaded and you are testing against what you want to test
If you have software (exe/dll) with uncertain/doubtful origin and you absolutely want to test it
(if it comes from a non respectful vendor i would strongly discourage you to install exe/dll, unless
you see the source code and are able to recompile it correctly, never take executables from
hacking site, they always include stuff you don't want on your system)
you can do a few things to limit your risk
1) you can always install software in a sandbox/virtual machine environment, if the software contains
a virus or other unwanted things, you will be able to contain the hazardeous behaviour to that sandbox
there are a lot of those environments out there. (vm ware, etc..)
2) if you don't have access to the source code and want to see what the software is doing, there a
few tools out that you can use :
- sniffer, is a program that allows to capture and visualize all packets that go in and out of your machine
this allows to see some of the network activity at least. (eg : ethereal, ..)
- you must of course always have a good end-node security product (anti-virus, malware detection)
- you can use a tool like filmon (system internals) to see what activity the module is generating on your
hard disk, if it is reading all files and directories on your disk, you might question what it's intent is)
Hi;
I want integrate my own DLL file to an indicator in NinjaTrader 8. But NT crashed when I compile my code.
I tried to do like explained in this tuto: "https://nexusfi.com/ninjatrader-programming/32855-ninjatrader-dll-s-creating-loading-how.html"]https://nexusfi.com/ninjatrader-programming/32855-ninjatrader-dll-s-creating-loading-how.html" , but that didn't work. I tried also to use AddOns section and that didn't resolve the problem.
This is my code:
#region Using declarations
using System;
using System.Collections.Generic;
using System.ComponentModel.DataAnnotations;
using System.Data;
using System.Data.SqlClient;
using System.Runtime.InteropServices;
using MyLibrary;
using NinjaTrader.Cbi;
#endregion
namespace NinjaTrader.NinjaScript.Indicators
{
public class MyIndicator : Indicator
{
private Export export = new Export();
private List<string> symbolDetails;
protected override void OnStateChange()
{
if (State == State.SetDefaults)
{
The example was created at the time that NT 8.0 was not yet out.
First thing that comes to my mind, is to check the .NET framework version.
To my knowledge NT 8.0 is using .net 4.5
For which version did you compile your DLL ?
Can you please check, correct and circle back if it solves ?
I already check it and my library has for target .NET framework 4.5. And it's compiled with VS 2015.
I think that the problem have relation with the instantiation of the object export: private Export export = new Export();. Because sometimes when I comment this line, the indicator works.
I would suggest you comment out the maximum of the logic inside that object
and get also a try/catch in place if some stuff is there
make sure that the container works, purely the object without anything else
Do you rely on any other DLL's inside your object ?
Can you post a screen shot when exactly it crashes ?
Is there something in the event log ?
something in other log files ?
Is the issue when you compile or when you try to execute the Indicator?
Your DLL needs to be in the /bin/custom/ folder and usually requires a restart of NT8 for NT8 to link to the code for use so make sure you have restarted. This could be a simple "can't find DLL". Please check your Log & Trace files for any hints, if you post them we might be able to help better.
