Announcement

Collapse
No announcement yet.

Partner 728x90

Collapse

NT65 import error on compiled assembly question

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    NT65 import error on compiled assembly question

    HI

    I have created a few custom indicators and compiled them into an assembly.
    Trying to move these indicators to a second NT 65 computer to test install etc.
    However, I get an import error.

    Import Failed. The existing Ninjascript file "MyDynamicPivots" contains duplicate method names ......
    What is interesting is that this indicator is no longer in my indicator folder or custom folder.
    It had been deleted long ago.

    Been reading in the forum that i may possibly have duplicate method name.
    I followed the instructions to manually compile the indicators on the second computer and then to add the dll (compiled assembly) to the custom folder. I then shut down ninja and restart.
    I opened one of the indicators i previously compiled; right clicked references and added the dll and tried to compile.

    I get the following message for @ADL.cs file.
    The Type 'NinjaTrader.Indicator.MyDynamicPivots' is defined in an assembly that is not referenced. You must add a reference to assembly 'DynPivotsWithSession, Version 1.0.0.1 Culture-neutral, publickeytoken=null'

    I am not certain how to proceed.
    MyDynamicPivots does not exist and either does DynPivotsWithSession as an assembly.

    there are no changes i can see in @ADL.cs file and the indicators are no longer on my computer.
    I also did a search within the .cs files in the inidcator folder to see if the inidcators were named differently... no trace of them anymore.
    Did something not clean itself properly on the delete way back when?
    Not certain how to proceed. Please advise....
    Thank you advance
    Sammy

    #2
    SammyC, is the reference to the Dynamic Pivots perhaps still listed in the References of the original PC you exported from?

    Comment


      #3
      Bertrand,
      At first first i thought that the assembly was not on the originating computer but I when i checked it did exist in the originating PC.
      Correction... there is an Assembly on the first PC.
      I am quite certain the code in my compiled inidcator assembly is completely self contained with no reference to that dll.

      How do i confirm there is no reference?
      I opened one of my indicators and then went into the references.
      That assembly and all my other packages dlls are there.

      Must I create the assembly on a PC with nothing else but the indicators i am compiling?
      Is there a way to exclude it/them?

      Thank you .... i would have never thought to check the originating computer.
      Sammy

      Comment


        #4
        Hi Sammy, yes I would complile the assemblies for export on a machine with only the needed indicator present - this will give you the cleanest DLL possible then.

        Comment


          #5
          Bertrand,
          Thank you kindly
          Sammy

          Comment

          Latest Posts

          Collapse

          Topics Statistics Last Post
          Started by argusthome, 03-08-2026, 10:06 AM
          0 responses
          88 views
          0 likes
          Last Post argusthome  
          Started by NabilKhattabi, 03-06-2026, 11:18 AM
          0 responses
          48 views
          0 likes
          Last Post NabilKhattabi  
          Started by Deep42, 03-06-2026, 12:28 AM
          0 responses
          31 views
          0 likes
          Last Post Deep42
          by Deep42
           
          Started by TheRealMorford, 03-05-2026, 06:15 PM
          0 responses
          34 views
          0 likes
          Last Post TheRealMorford  
          Started by Mindset, 02-28-2026, 06:16 AM
          0 responses
          69 views
          0 likes
          Last Post Mindset
          by Mindset
           
          Working...
          X