Support Board
Date/Time: Sat, 05 Jul 2025 13:27:04 +0000
[Programming Help] - newly compiled debug DLLs won't load anymore after updating to latest VS 2022 version
View Count: 318
| [2024-11-23 23:25:12] |
| ycomp - Posts: 324 |
|
I have an instance of Sierra I that I use for Development. These DLLs loaded fine before, and I could compile them with VS 2022 in Debug mode and load them no problem. I made a few minor code modifications and compiled them and they won't load. I think the problem is not from my code changes but because I updated VS 2022 yesterday. I mean that is my guess, since I didn't really do anything complicated or change and project settings. Compiled release versions of the DLL work in another instance of Sierra I use for trading. I mean that were also compiled by this updated VS 2022 but compiled in release mode and used in my trading instance. What could be causing this? 2024-11-23 18:19:43.130 | yDisplayInfo.dll loading error. Windows error code 127: The specified procedure could not be found. 2024-11-23 18:19:43.130 | InternalVersionNumberToFileNameMap is empty for yDisplayInfo |
| [2024-11-24 01:24:45] |
| ondafringe - Posts: 325 |
|
Files might be corrupted. To check: Close SC, go to Data folder, and delete the .dll and all related files (.exp, .lib., .pdb). Rebuild and redeploy to see if that helps.
Date Time Of Last Edit: 2024-11-24 14:12:53
|
| [2024-11-24 14:56:26] |
| ycomp - Posts: 324 |
|
thanks, I tried to delete the DLL and all associated files in the Data folder, and I still get the same messages. These messages appear in the message log when I open the "Add Study" Dialog. The dlls also do not show up in the "Add Study" Dialog. In addition the messages already displayed, I also get the message 2024-11-24 09:50:43.249 | Closest match search for: D:\SierraChart DEV\Data\yDisplayInfo.dll returned empty result. *
These messages I gave are for one DLL with studies but I also have the same problem with 2 other DLLs. These are all the DLLs which I have compiled since I updated VS 2022 some days ago. The DLLs run when compiled for release mode in my Trading instance of Sierra. The problem is with the debug DLLs that I use in my instance of Sierra that I use for Development. |
| [2024-11-24 16:19:16] |
| ondafringe - Posts: 325 |
|
If you are building/deploying your dll from within VS, Release and Debug each have unique configurations. Since Release works and Debug doesn't, maybe the VS update altered your Debug configuration. Have you double-checked those settings to make certain they are still valid? If those settings are still valid, you might make a backup copy of your cpp file and then undo the changes you mentioned earlier just to make sure those changes didn't cause the problem. Now if you are only using VS as an editor, and building from within SC, not sure what to tell you because I do everything from within VS. |
| [2024-11-24 20:21:10] |
| ycomp - Posts: 324 |
|
yes I use VS 2022 for everything ah you know what the difference is between the debug and release DLLs, the debug ones use clang_rt.asan_dynamic-x86_64.dll.. I wonder if it is possible that updating VS 2022 could somehow cause problems loading this dependency.. it is still in the data folder where it should be asan is an address sanitizer Date Time Of Last Edit: 2024-11-24 20:22:00
|
| [2024-11-24 20:33:57] |
| ycomp - Posts: 324 |
|
yes that fixed it, there are a new version of this DLL that VS 2022 installed in the VS build tools folder when it updated VS 2022. So I copied that over the one I had in Data.
|
| [2024-11-24 21:35:20] |
| ondafringe - Posts: 325 |
|
Glad you got it worked out. :)
|
To post a message in this thread, you need to log in with your Sierra Chart account: