Support Board
Date/Time: Thu, 15 Oct 2026 17:39:15 +0000
Versioned custom study DLL name: ARM64 form, and a number higher than the running version
View Count: 46
| [2026-10-15 12:44:37] |
| cferry - Posts: 18 |
|
We distribute custom studies through the custom studies file server and now serve x64 builds for version 2962 and higher; our ARM64 builds are ready but not served yet. Following "Custom Study DLL File Name Format", we add [DLLName]_<N>_64.dll next to the existing [DLLName]_64.dll, where N is the SC_DLL_VERSION of the headers we build against, and the file server serves it with the rule "Greater or Equal to N". What we measured on x64. On 2899, with both files present, [DLLName]_64.dll loads; with the versioned file alone, the message is "requires version 2963 or higher of Sierra Chart". On 2971, whose headers carry SC_DLL_VERSION 2969, [DLLName]_2969_64.dll loads and runs, and so does the same file renamed [DLLName]_2971_64.dll. Only one versioned file is loaded, the highest one present. On 2971, with _2963 and _2968 present, _2968 is selected and refused ("needs to be recompiled to be used on this version"). Adding _2969 makes it the one loaded. Two points we could not test: 1) ARM64. The documentation page only gives the x64 form, and we have no ARM64 machine. Is the versioned name [DLLName]_<N>_ARM64.dll, and does SierraChart_ARM64.exe follow the same rules as above, including on versions older than 2962? 2) A number in the file name higher than the running version, on 2962 and higher: for example [DLLName]_2971_64.dll on 2969 or 2970. Is that file skipped, or selected and then refused? Until we know, N stays at the SC_DLL_VERSION of the headers. |
| [2026-10-15 14:55:00] |
| ForgivingComputers.com - Posts: 1243 |
|
1. Yes. 2. Selected. If running 2971 and MyStudy_2971.cpp is built with 2969 headers. Version 2969 will support the study. |
To post a message in this thread, you need to log in with your Sierra Chart account: