-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Including native libraries in dotnet projects without nuget package #7017
Comments
MSBuild allows this very easily using the |
@nicolasr75 try using |
@tmds thanks, indeed it seems to be as easy as
I somehow thought I'd have to create all the runtime directories dynamically and copy the DLL to all of them. In my case the DLL is the same for all runtimes and it works by simply copying it to the publish base directory. |
@blackdwarf yes, I guess |
@nicolasr75 I will assume that this worked since MSbuild's |
According to the current documentation the packOptions would allow us to specify a native library for inclusion in a nuget package. Wouldn't it be great if we could have something similar for a normal app publish? That would allow us to bypass the creation of a nuget package for simple scenarios.
For example:
From my tests it looks like packOptions is not considered by dotnet publish.
https://docs.microsoft.com/de-de/dotnet/articles/core/tutorials/libraries
The text was updated successfully, but these errors were encountered: