DllExport Manager Q A

DllExport Manager. Q/A

We finally changed distribution of our packages starting with v1.6 release.

Now you can easily use our tool via lightweight embeddable manager for all your amazing things.

Why we did it ?

Unfortunately, the modern NuGet project no longer meets our needs, which would mean more difficult support. -"We are not a library, we're tool."

Is this cross-platform solution ?

Yes. The main batch script file DllExport.bat was based on GetNuTool core that's Cross-Platform Embeddable Package Manager that requires only MSBuild. Finally it just aggregates calling to Wizard that was based on MvsSln. So it very easy to continue use this for any other platform.

However, today's DllExport project still does not support .net core. Therefore, we also do not provide some other wrapper for linux (etc) at this time. Like and the Wizard (which still provides only Windows.Forms UI layout).

Does this provide automatic restoring also like nuget ?

Yes. You don't need to do anything else after initial configuration. It should be automatically restored by any Build operation for your configured projects.

• Automatic Package Restore. For MSBuild / CI.
• Automatic Package Restore. For Visual Studio.

Should I have the installed Powershell ?

No. Neither Powershell nor dotnet-cli. You don't need this at all.

I just don't like additional files in my repo. What to do ?

Our manager is fully embeddable. You can combine it with other your scripts (even with other batch files) or just integrate this inside project files.

But you can also receive this directly from server before build (less than 20 kb text-based file): https://3F.github.io/DllExport/releases/latest/manager/

Where I can look examples about using ?

• Screencast:
  • .NET DllExport - Quick start (Configuring, Automatic restoring, Pe-Viewer)