Downloads of v 1.2.7
Unmanaged Exports (DllExport for .Net)
A set of compile-time libraries (nothing to deploy) and a build task that enable you to export functions from managed code to native applications.
That means, you can create plugins in a managed language like C# or F# for native applications that only have a C-Api (like Notepad++).
The nuget package is all you need. Just mark your methods with [DllExport] and build for x86, x64 or ia64.
- You have to set your platform target to either x86, ia64 or x64. AnyCPU assemblies cannot export functions.
- The export name defaults to the method name and the calling convention to stdcall. If that's all what you want, you can just use [DllExport] without parameters.
- You cannot put your exports in generic types or export generic methods. (The CLR wouldn't know what type parameters to use)
To install Unmanaged Exports (DllExport for .Net), run the following command in the Package Manager Console
PM> Install-Package UnmanagedExports
- will use the most recent version of Microsoft.Build.Utilities.ToolLocationHelper to have a greater chance of finding the exact ildasm/ilasm for the project's target framework version
- no longer fails the build when it can't find lib.exe
- proper overridable MSBuild properties (see tools/RGiesecke.DllExport.targets)
This package has no dependencies.
|Unmanaged Exports... 1.2.7 (this version)||387||Sunday, August 16 2015|
|Unmanaged Exports... 1.2.6||12264||Thursday, November 07 2013|
|Unmanaged Exports... 126.96.36.19922-Debug||630||Wednesday, June 26 2013|
|Unmanaged Exports... 188.8.131.5262||2298||Monday, March 11 2013|
|Unmanaged Exports... 1.2.3-Beta||387||Thursday, December 20 2012|
|Unmanaged Exports... 184.108.40.20607||1066||Monday, October 29 2012|
|Unmanaged Exports... 220.127.116.11778||197||Wednesday, October 17 2012|