Announcement
Collapse
Looking for a User App or Add-On built by the NinjaTrader community?
Visit NinjaTrader EcoSystem and our free User App Share!
Have a question for the NinjaScript developer community? Open a new thread in our NinjaScript File Sharing Discussion Forum!
Have a question for the NinjaScript developer community? Open a new thread in our NinjaScript File Sharing Discussion Forum!
See more
See less
Partner 728x90
Collapse
NinjaTrader
Error importing compiled indicator
Collapse
X
-
Error importing compiled indicator
I have an indicator that references two other custom indicators and I am compiling it to a .cs and .dll . When others try to import they get this error (attached). The blacked out indicator is a third party (and salamander protected) indicator we all use. I have changed all the dataseries, variable names, etc in the three indicators that compile together and nothing works. If not compiled they import with no problem but I dont want the code exposed. Any ideas?Tags: None
-
I'm sure that would work but that indicator package is part of the trading strategy. That is not the answer. My indicator is designed to be used in conjunction with the other assembly while not actually accessing it since the other is protected.Last edited by eDanny; 04-02-2009, 04:36 PM.
Comment
-
You are mistaken, I am not including anything but my indicators, which dont even reference the other custom assembly at all. Two of my indicators are used to duplicate some of the output of the third party assembly, without using the same code, so that my third indicator can use that data to do what it does. There is no connection at all and yet the error suggests there is. How could I be using duplicate method names since I cant see the code from the other assembly? As I said, I have changed the names of all dataseries and variables in all three of my indicators and still the issue exists.
Comment
-
Originally posted by NinjaTrader_Josh View PosteDanny,
Any use of enums?
Comment
-
Yes I already found out that wont work while testing it myself. They have no uncompiled versions. Even if they did, the error would be different. Just explain to me exactly what that error would normally mean. How can someone elses indicator, totally unrelated to mine, affect mine like that?
Comment
-
Originally posted by NinjaTrader_Josh View PosteDanny,
As stated, we are out of ideas. Please try exporting as assembly some other basic scripts.
Back to my original indicator. Since the other users who had problems trying to import my indicator had a different version of some of these assemblies, they were not able to import. I had to remove my assemblies in order to export an indicator that wouldnt require those assemblies on being imported. That is just wrong. Nothing should be required that isnt called in the indicator!Last edited by eDanny; 04-03-2009, 12:45 PM.
Comment
-
Originally posted by NinjaTrader_Josh View PosteDanny,
If you are experiencing such behavior there is something likely wrong with your NinjaScript environment. I suggest you try to get yourself a clean reinstall and see if you can export as assembly then.
Comment
Latest Posts
Collapse
Topics | Statistics | Last Post | ||
---|---|---|---|---|
Hi
by AveryFlynn
Started by AveryFlynn, Today, 04:57 AM
|
1 response
10 views
0 likes
|
Last Post Today, 07:57 AM | ||
Started by Max238, Today, 01:28 AM
|
4 responses
37 views
0 likes
|
Last Post
by Max238
Today, 07:49 AM
|
||
Started by r68cervera, Today, 05:29 AM
|
1 response
8 views
0 likes
|
Last Post Today, 07:47 AM | ||
Started by geddyisodin, Today, 05:20 AM
|
1 response
11 views
0 likes
|
Last Post Today, 07:38 AM | ||
Started by timko, Today, 06:45 AM
|
2 responses
14 views
0 likes
|
Last Post Today, 07:30 AM |
Comment