Can't fix it Unable to load DLL 'tdjson.dll' or one of its dependencies #164
-
In the development environment, everything was fine, the project worked. It's time to transfer to the server, got the following error: at Program.(String[] args) I'm new to programming and can't figure this out on my own. I would really appreciate help. |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 7 replies
-
What exactly have you transferred to server? Is |
Beta Was this translation helpful? Give feedback.
-
I was also confused, when building I was told to build with all the dependencies, and the necessary library was in the build, but there was still an error. Next, I just ran the exe file. Of course, the mistake is in my actions, and I would like to understand in what actions. |
Beta Was this translation helpful? Give feedback.
-
Opened the project on the server through visual studio, and installed through the Nuget library. And then dotnet build and then from the bin folder I was able to run myProgram.exe |
Beta Was this translation helpful? Give feedback.
-
Normally, if you deploy Note, though, that Windows build of For investigation of such cases, I recommend using Process Monitor: set it up to filter file activity of your process and look for failed file opening attempts. That will help to determine which DLLs it looks for, and at what paths. If there's a failed query for |
Beta Was this translation helpful? Give feedback.
-
I understand roughly what you are talking about, I think I will still face
this problem since I will have to work with your library. Thanks for the
time.
вс, 2 апр. 2023 г. в 18:48, Friedrich von Never ***@***.***>:
… Normally, if you deploy tdjson.dll alongside your program, it all should
work correctly.
Note, though, that Windows build of tdjson.dll deployed as a part of
tdlib.native (which you may or may not use, this is your choice) may depend
on Visual Studio C++ runtime, that may have to be installed separately
(that's mentioned in the documentation
<https://github.com/ForNeVeR/tdlib.native#library-dependencies>).
For investigation of such cases, I recommend using Process Monitor
<https://learn.microsoft.com/en-us/sysinternals/downloads/procmon>: set
it up to filter file activity of your process and look for failed file
opening attempts. That will help to determine which DLLs it looks for, and
at what paths. If there's a failed query for vcruntime*.dll, that means
you have no required runtime version installed. If it fails to load
something like api-ms-*.dll, then that means UCRT is not installed. The
latter usually comes with Windows updates, but god that's messy.
—
Reply to this email directly, view it on GitHub
<#164 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AS4IWWITCVK3BOAGBD6GWHDW7FKPRANCNFSM6AAAAAAWEPQUJE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
Normally, if you deploy
tdjson.dll
alongside your program, it all should work correctly.Note, though, that Windows build of
tdjson.dll
deployed as a part of tdlib.native (which you may or may not use, this is your choice) may depend on Visual Studio C++ runtime, that may have to be installed separately (that's mentioned in the documentation).For investigation of such cases, I recommend using Process Monitor: set it up to filter file activity of your process and look for failed file opening attempts. That will help to determine which DLLs it looks for, and at what paths. If there's a failed query for
vcruntime*.dll
, that means you have no required runtime version installed. If it fails t…