Duplicate Method Names

[dontpanic]

Hi,

I am getting the duplicate method names error when importing my custom indicator.

I have scanned the forums and the suggested fixes have not helped me, but I can add that -

- The error occurs whether or not I use CliSecure to encrypt
- I have tried importing my indicator into a fresh and clean installation of NT, with no custom source files installed
- I can copy the source file to the fresh NT installation and compile it without error
- the source file includes one public enum
- the source file uses the VOL.cs file which it says it needs to include when it exports

Any suggestions?

Thanks,
Will.

[NinjaTrader_CalH]

Will,

Thank you for your posting.

I believe this is because of the public enum that you are calling. If you are calling that public enum from any other indicator NinjaTrader will see this as a duplicate method error.

Is this being called within the Indicator class or outside of it?

[dontpanic]

Hi Cal,

I doubt that there is another indicator with the same name because I am trying to install it on a clean installation of NT.

It is declared outside the namespace, and used only within the indicator.

note that it compiles and run's fine, its only when I export it and then try to import it that the problem occurs.

Will.

[NinjaTrader_CalH]

Will,

Are you importing the system on the same computer you have the source code?

[dontpanic]

No, its a different computer with a fresh install of NT.

[NinjaTrader_CalH]

Will,

Can you send me the exported zip folder, so that I may test it on my end?

You can send the folder to support[at]ninjatrader[dot]com with ATTN Cal in the subject and a reference to this thread in the body.

Thank you for your patience.

[neoikon]

Was a solution found for this? Is there a particular coding practice that causes this to happen?

Fortunately, I know how to undo the problem (if the import breaks NinjaTrader), but not prevent it from happening.

The behavior seems to vary from machine to machine as well, which makes it difficult to debug.

Thanks!

[dontpanic]

No,

I did not find a solution. From memory I think I ended up renaming the enum and the problem went away... even though I could not find that enum anywhere else.