You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to control a Drive via C# using SOEM to communicate with it. To do so, I created a .dll using the SOEM Library and am now trying to use that with DLLImport, though I get an error that the DLL could not be loaded since a specified module could not be found. Upon further investigation using dumpbin, it lists VCRUNTIME140D.dll as one of its dependencies, which seems to be a debug version of a Microsoft C Runtime Library.
Ideally in my release I'd like to not have a debug version of a runtime as a dependency, do you know if there's something that can be done here?
I know it's kind of a long shot since as far as I can tell, this doesn't seem to be a very common usage of the Library ^^'
Kind Regards
The text was updated successfully, but these errors were encountered:
Hey, this might be a weird use-case ^^
I'm trying to control a Drive via C# using SOEM to communicate with it. To do so, I created a .dll using the SOEM Library and am now trying to use that with DLLImport, though I get an error that the DLL could not be loaded since a specified module could not be found. Upon further investigation using dumpbin, it lists VCRUNTIME140D.dll as one of its dependencies, which seems to be a debug version of a Microsoft C Runtime Library.
Ideally in my release I'd like to not have a debug version of a runtime as a dependency, do you know if there's something that can be done here?
I know it's kind of a long shot since as far as I can tell, this doesn't seem to be a very common usage of the Library ^^'
Kind Regards
The text was updated successfully, but these errors were encountered: