Skip to content

DllExport Manager Q A

Jump to bottom Edit New page
Denis Kuzmin (github/3F) edited this page Jun 10, 2025 · 4 revisions

DllExport Manager. Q/A

We have finally changed the distribution of our packages starting with 1.6 release.

Now you can use our tool more easily through a lightweight built-in manager for all your amazing things.

Why we did it ?

Unfortunately, the modern NuGet project no longer meets our needs due to more complex support. -"We are not a library, we're tool."

Do I need to configure every time when build is started ?

No. Don't do this, it's bad practice. If you need custom automation, define an external storage and use -action Recover etc.

Does someone need to configure every time my project is distributed or clonned together with ?

No. It's bad practice. You can set it up once, then it will be applied every time someone does an automatic restore.

But if you need more automation, define an external storage and use -action Recover etc.

Does this provide automatic restoring like NuGet ?

Yes. You don't need to do anything else after initial setup. It should be restored automatically during any build operation by *default (can be disabled, see 🗎 Restoring package).

Do I need to have the Powershell or dotnet-cli ?

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

Does DllExport support NuGet somehow ?

Most likely yes. But NuGet features are not guaranteed (tl;dr something may not work or not work properly)

Do I need to store extra .dll or .exe in my repository ?

No. You don't need to store anything like .dll, or .exe, etc if you are using the main online edition. Moreover, it is bad practice to do this.

I don't have access to the internet at the build stage. How can I use your tool?

For your convenience, the .NET DllExport also provides the following:

Is this cross-platform solution ?

The manager was based entirely on hMSBuild (built-in +-> GetNuTool) and relies on MvsSln which provides cross-platform support. It is very easy to adapt only basic shell scripts also for Linux etc. But it's not ready yet.

However, the project itself does not yet support other platforms. Because we use our own assembler which is currently released only for Windows. And other little things that don't allow us to achieve cross-platform yet. Maybe later.

What is or Where is DllExport_Configure.bat ?

DllExport manager from 1.6.x had no default action at all; Starting with 1.7 the default is -action Configure. You no longer need to type it manually or have DllExport_Configure.bat or like. If you still have it, feel free to delete it; it won't affect anything.

I don't like extra files in my repository. What to do ?

DllExport manager is fully embeddable ~28 KB of basic shell script. You can combine it with other scripts including batch (.bat) or just integrate it into your project files etc. Or get it right before build in any way convenient for you: https://3F.github.io/DllExport/releases/latest/manager/

You don't need to store anything else (.dll, .exe,...) in your repository. Don't do this, it's bad practice.

Where can I see usage ?

Except where otherwise noted, wiki content is licensed under a Creative Commons Attribution 4.0 International License. (CC BY 4.0).

🗎

🗔

📂

Clone this wiki locally