-
-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Empty function table after export #136
Comments
Can you show what says Also I hope you're using modified modules in related x86 + x64 folders instead of original in ~\bin. |
Log: PS D:\Documents\Visual Studio 2019\Projects\ClassLibrary1> .\DllExport.bat -pe-exp-list bin\Debug\netstandard2.1\ClassLibrary1.dll
PS D:\Documents\Visual Studio 2019\Projects\ClassLibrary1> .\DllExport.bat -pe-exp-list bin\Debug\netstandard2.1\x86\ClassLibrary1.dll
PassThruClose
PassThruConnect
PassThruDisconnect
PassThruGetLastError
PassThruIoctl
PassThruOpen
PassThruReadMsgs
PassThruReadVersion
PassThruSetProgrammingVoltage
PassThruStartMsgFilter
PassThruStartPeriodicMsg
PassThruStopMsgFilter
PassThruStopPeriodicMsg
PassThruWriteMsgs
PS D:\Documents\Visual Studio 2019\Projects\ClassLibrary1> .\DllExport.bat -pe-exp-list bin\Debug\netstandard2.1\x64\ClassLibrary1.dll
PassThruClose
PassThruConnect
PassThruDisconnect
PassThruGetLastError
PassThruIoctl
PassThruOpen
PassThruReadMsgs
PassThruReadVersion
PassThruSetProgrammingVoltage
PassThruStartMsgFilter
PassThruStartPeriodicMsg
PassThruStopMsgFilter
PassThruStopPeriodicMsg
PassThruWriteMsgs
PS D:\Documents\Visual Studio 2019\Projects\ClassLibrary1> I'm trying to use from the x86 folder, because 32-bit is required :) |
@gimi87, Thanks for the details about issue! I don't know about "DLL Export Viewer" tool, but our -pe-exp-list indicates normal export as you can also see it from your log.
You need to contact with developers of the mentioned "DLL Export Viewer" tool if some records are not displayed from the following modules:
|
I know that it is 3rd party tool. |
I could not get a .NET Standard 2.1 assembly to be callable from native code without access violations. Simply switching to .NET Standard 2.0 made it work, but only after I also set the following project properties, which I took from the Example repository (which is also only targeting .NET Standard 2.0):
|
@3F I may have missed that info elsewhere, but is .NET Standard 2.1 even meant to be supported at this time? As said in my above comment, I could not get it to work, it only throws access violations when trying to call the exported functions from native code. I can accept a sample project if you like. |
Please read #132 as I mentioned above. For today I implemented rebasing only for system objects: #125 (comment) For better support and most known behavior with 1.7.0, Follow the news! |
Thanks for the information! |
Hello :)
I guess I have a simple problem with the DllExport.
I have
netstandard2.1
project and I'm running theDllExport 1.7.0
version and I'd like to export functions.This is my csproj:
sample class:
build log:
After that I have a program called "DLL Export Viewer" to check that export is correct and file is generating proper function table and my list is empty:
Similar library from 3rd party is looking like this:
What I'm doing wrong? Can you help me to fill that table with your tool?
The text was updated successfully, but these errors were encountered: