I am developing a .NET Standard library and plan to use it in both .NET Core and .NET Framework projects. My library is dependant on a third library which itself is dependant on a few C binary files. The C binary files have to be copied to the output directory of the project which will be referencing my library.

I added the binary files to my library project as content and they are copied to the `content` and `contentFiles` directories when the NuGet package is packed with the `dotnet pack` command. The files are also listed in the `nuspec` file.

---

However when I install the NuGet package there are two different behaviours to observe depending if I install it to a .NET Framework or .NET Core project:

### .NET Framework

The binary files I added to my library project are also added to the referencing project and I can copy them to the output directory. This is the behaviour that I expect, want and works.

### .NET Core

The binary files I added to my library project are also added to the referencing project **but** as links which also works but ***only** on my machine* of course since the NuGet packages are stored in the Windows user folder by default. This create problems for anyone else that will work on the same project on a different machine as the links to the files are broken in that case.

---

I already tried messing around with the `nuspec` file itself but this doesn't really help since I only get the `nuspec` file after packing which is done by CI pipeline.

Why is the behaviour for .NET Framework and .NET Core project different in that case and is it possible to get the behaviour of a .NET Framework project in a .NET Core project?