Support Board
Date/Time: Tue, 10 Nov 2026 23:56:09 +0000
Post From: Custom Study Remote Build or custom study enumeration changes lately??
| [2026-11-10 22:21:54] |
| User275839 - Posts: 76 |
|
Well so that is very interesting... The behavior you are seeing is basically what I want. And it appears that the build process picks up the DLL name from the SCDLLName define at the file start. One possibly informative oddity... When I recompiled older studies they would show the desired labeling in the filename and module name, and in the parenthesis as well. New builds of new .cpp files don't show the _v01, ... in the parens -- just the SCSFExport function name. I have never put multiple exported function declarations within a single module so I'm not sure about your example showing that. However, in your I am puzzled by why the v3 DLL shows a v3 and v4 function, but there is no function named _v3 in the file. See the attached image to see what my Add Study dialog shows for a new file/new compile (top line) and an old study file recompiled yesterday (bottom line). There are 3 items of interest for me here: - the name of the Study DLL - the string within the parens with the v2969 appended) - the name of the function within the DLL where in the .cpp file do each of those items come from? Date Time Of Last Edit: 2026-11-10 22:29:25
|
| |
