Announcement

Collapse
No announcement yet.

Partner 728x90

Collapse

Correct way to include dll files / use of AdditionalReferences.txt

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

    Correct way to include dll files / use of AdditionalReferences.txt

    I put together a few indicators and bundled these indicators into a 'all in one' indicator zip file - in that file I also added copies of a few needed framework dll files (e.g. System.Management.dll).

    Another user got the problem now that he uses an indicator package from another vendor which also uses the System.Management.dll file but this vendor didn't put the dll file itself into their indicator zip but only referenced the System.Management.dll file in the AdditionalReferences.txt ("*Windows*\Microsoft.NET\Framework64\v4.0.30319\S ystem.Management.dll").

    This ends in unhandled exception errors when both indicators are used at the same time....

    So I wonder what is the correct/best way to 'bundle' such dll files from the .NET Framework.

    - I think the better way is to not copy the dll file itself into the indicator zip file but use the AdditionalReferences.txt file and put in there a line with e.g. "*Windows*\Microsoft.NET\Framework64\v4.0.30319\Sy stem.Management.dll" - correct?
    - Am I right in assuming that a windows update updates the files in that Windows\Microsoft.NET\Framework64\* directory?
    - If these dll files gets updated in there is the folder name also changed (now "v4.0.30319")?
    - If yes how often this folder name / version changes because if so I always have to check if this folder name is still the same, if not I have to correct that reference in the AdditionalReferences.txt file and put out an update for my indicator itself?

    Thanks

    #2
    Hi Heart, thanks for posting.

    The best way to distribute the extra DLL file is to add it to your .zip folder. This .NET location Microsoft.NET\Framework64\v4.0.30319\System.Manage ment.dll can change and if this is not programmatically generated at startup/install it can break in the future. Follow this guide on adding the DLL to the export:



    There is also a video guide here:



    Kind regards,
    -ChrisL

    Comment


      #3
      Originally posted by NinjaTrader_ChrisL View Post
      The best way to distribute the extra DLL file is to add it to your .zip folder.
      So I already 'did it right' by adding the dll file itself to my indicator zip file. But as mentioned in post 1 this user has another indicator installed which does it with the other method (referencing Microsoft.NET\Framework64\v4.0.30319\System.Manage ment.dll) and so he gets unhandled exception errors when using both indicators. How can this be solved?

      Comment


        #4
        Hi Heart, thanks for the follow up. The other indicator should not be referencing the DLL in this way, it goes out of the best practice so it would be up to the developer of that script to change it.

        Kind regards,
        -ChrisL

        Comment

        Latest Posts

        Collapse

        Topics Statistics Last Post
        Started by Geovanny Suaza, 02-11-2026, 06:32 PM
        0 responses
        649 views
        0 likes
        Last Post Geovanny Suaza  
        Started by Geovanny Suaza, 02-11-2026, 05:51 PM
        0 responses
        370 views
        1 like
        Last Post Geovanny Suaza  
        Started by Mindset, 02-09-2026, 11:44 AM
        0 responses
        109 views
        0 likes
        Last Post Mindset
        by Mindset
         
        Started by Geovanny Suaza, 02-02-2026, 12:30 PM
        0 responses
        573 views
        1 like
        Last Post Geovanny Suaza  
        Started by RFrosty, 01-28-2026, 06:49 PM
        0 responses
        576 views
        1 like
        Last Post RFrosty
        by RFrosty
         
        Working...
        X