-
-
Notifications
You must be signed in to change notification settings - Fork 144
.Net Core
.NET DllExport is ready for .NET Core projects starting with v1.7 release
For better support and most known behavior with 1.7.x, netstandard2.0 or netcoreapp2.2 is recommended. [?]
1.8+ Extends support for netcore projects via the same rebasing feature (part of 3F's IL Assembler) and also provides control around .typeref directives.
Two rebasing modes: with and without merging for both ILMerge / ILRepack;
Project configuration and usage can be seen in our real tests. For example, here for net9.0;net8.0;net7.0;net6.0;net5.0;netcoreapp3.1;netstandard2.1;netstandard2.0;...
To access the mentioned code and configuration,
- Clone and prepare the environment:
git clone https://github.com/3F/DllExport.git src
cd src & git checkout -qf c2d3cd1e6febe3b6f72bb59
.\build Debug-
Then you will be able to run
DllExport.assets.cmdandassets.slnin the cloned directorysrc.- points to src/DllExport/assets (NetCore, NetCoreRef, Net5OrLess, Netfx, NetfxLegacy, ...)
-
Finally test these assets using
DllExport.sln->UnitedTest
Here you can also find ExtDotNetCoreLibrary4 (net9.0;net8.0;netstandard2.1) that was configured for basic netcore assemblies with multiple targeting (TargetFrameworks).
For other types support find actual Unit tests here (net9.0;net8.0;net7.0;net6.0;net5.0;netcoreapp3.1;netstandard2.1;netstandard2.0)
Except where otherwise noted, wiki content is licensed under a Creative Commons Attribution 4.0 International License. (CC BY 4.0).
π
- π Home
- π Quick start
- π First function
- π Data types
- π .Net Core
- π Export
- π Pre-processing
- π Conari
- π ILMerge & ILRepack
- π [x]AssemblyResolve
- π Post-processing
- π Examples
- π C++ and C# ([+]πΉ)
- π string & struct ([+]πΉ)
- π§ͺ Demo
π
- π DllExport Manager
π
- π Q / A