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)
If you export using NT, then NT will take care when you import back and will place everything where it belongs.
Only problem could be if you are referencing 3rd party assemblies which are not included in zip
Can you help answer these questions from other members on NexusFi?
ok i got a friend that is trying it tonight. we will see how it goes. I just want to share it with the elite when its done.
and one last question , when you say third party do you mean me?? cause the dll used is not native to ninja install. I placed it there on my machine to get things to work. I just hope it works lol. If so its not a big deal i built a installer just for the dll's then they can just import the zip for the indicator.
I apologize for all the questions i never dealt with dll's until a week ago.
thanks again bukken I finally figured all this out with your help. I cannot tell you how much I appreciate it. What a great thing. Now it loads my dll and everything WOOHOO. this will defined simplify it for others.
Sure monpere. Then maybe you will know another thing I am wondering about.
Ok so we built ourselves a snazzy custom indicator in ninja. And unfortunately this indicator uses an external dll. We now want to share it with others but many are thrown off by the place this here do that etc. And usually they end up putting this file in the wrong place. So then they bother you asking what happened.
So first we built our snazzy new Indicator. We added the reference to the dll.
I will use my trade tracker as an example.
So we go into ninja and do the typical export.
A window will pop up warning that you need to be aware the target pc needs to have certain files on it.
(very important note, if you reference a different dll for a different file you should remove those files in a safe place before exporting this file. Because ninja will want all those on the target pc.) I am unsure as of this typing if u jsut remove those references if it needs them if it will still look for them.
Ok so now you have a folder zip. open that and you will see a file that says additonal references. check that the name of needed dll / dll's are in it. And not uneeded ones.
Add your dll to the root of this zip
and WALLA like majic ninja loads your dll on the users pc upon import. After i got it to work i sat and stared for like 5 mins goin your kidding right. I been building a custom installer etc and it was just place the file here.
after import into ninja a warning will come up saying the pc needs the dll to work right. But it is there and this is just a friendly warning. Restart ninja and use the custom indicator.
So i managed to figure out how to build a form in visual basic then have ninja load it. Now here is my loading code.
TestForm.Show();
which loads the form
now that form has a button. But i cannot seem to gain access to the button I am curious how.
to make it simple i was trying to jsut have when i click the button a message box opens. But i am unsure how to get the ninja .cs to know if the button was clicked in the form in the dll
So I am still working on this I got the form to load via the script I posted earlier and i am now trying to access the button on it. I think in the visual studio project i need to add variables that ninja can acces and maybe a public something to show ninja that the button was clicked. Still working ................
maybe instead of using the dll i could just reference a .cs namespace or something. hmmmm
Tim