DllExporterNet4 1.0.0

Used to export native-code-like functions from a .NET assembly

Install-Package DllExporterNet4 -Version 1.0.0

dotnet add package DllExporterNet4 --version 1.0.0

<PackageReference Include="DllExporterNet4" Version="1.0.0" />

For projects that support PackageReference, copy this XML node into the project file to reference the package.

paket add DllExporterNet4 --version 1.0.0

The NuGet Team does not provide support for this client. Please contact its maintainers for support.

Documentation

Usage:

Add reference to DllExporterNet4.exe to your assembly project.
Add DllExporter.DllExport attribute to static methods that will be exported.
Add following post-build command to project properties:
DllExporterNet4.exe $(TargetFileName)
move $(TargetName).Exports$(TargetExt) $(TargetFileName)
Build project.

See also this: https://stackoverflow.com/questions/8957970/how-do-you-export-a-method-in-a-cil-dll-so-that-a-native-program-can-call-it

This does end up putting the .pdb in a weird place which is hard coded into your resulting DLL. Worth knowing if you have trouble with the debugging.

Usage:

Add reference to DllExporterNet4.exe to your assembly project.
Add DllExporter.DllExport attribute to static methods that will be exported.
Add following post-build command to project properties:
DllExporterNet4.exe $(TargetFileName)
move $(TargetName).Exports$(TargetExt) $(TargetFileName)
Build project.

See also this: https://stackoverflow.com/questions/8957970/how-do-you-export-a-method-in-a-cil-dll-so-that-a-native-program-can-call-it

This does end up putting the .pdb in a weird place which is hard coded into your resulting DLL. Worth knowing if you have trouble with the debugging.

Initial release.

This package has no dependencies.

This package is not used by any NuGet packages.

This package is not used by any popular GitHub repositories.

Version	Downloads	Last updated
1.0.0	366	2/21/2019