Error importing compiled indicator

[eDanny]

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?

[NinjaTrader_JoshP]

eDanny,

Please have them remove all instances of the common indicator you guys share and see if they can import after.

[eDanny]

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.

[NinjaTrader_JoshP]

If you are only using it don't include it in your own package then.

[eDanny]

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.

[NinjaTrader_JoshP]

eDanny,

Any use of enums?

[eDanny]

eDanny,

Any use of enums?

No use of any advanced techniques.

[NinjaTrader_JoshP]

Sorry I am out of ideas then. Please be sure that they do not have the uncompiled assembly version installed on their NinjaTrader before trying to import the assembly.

[eDanny]

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?

[NinjaTrader_JoshP]

It is a generic error box informing you that there is some conflict between some file they have and your script.

[eDanny]

Any idea why a person can import and use when not compiled into an assembly but cannot import the assembly?

[NinjaTrader_JoshP]

eDanny,

As stated, we are out of ideas. Please try exporting as assembly some other basic scripts.

[eDanny]

eDanny,

As stated, we are out of ideas. Please try exporting as assembly some other basic scripts.

I tried that and found a bug (I believe) in NT. When trying to export and compile another unrelated indicator I was informed that in order to import it I would have to have two 3rd party indicators installed. There was no relation between these indicators but since I had those assemblies installed, NT requires them for any other person to import! How crazy is that???

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!

[NinjaTrader_JoshP]

eDanny,

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.

[eDanny]

eDanny,

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.

Ok I'll give that a try.