How to force nuget package reference dlls to be copied to output directory?

Question

I added the System.Memory Nuget Package to my net48 Azure Function V1 project to provide the missing dlls for a referenced netstandard2.0 package. But as the package is not directly used in my code, the dlls are not copied to the output folder.

How can I force the dlls of the System.Memory package to be copied to the output folder on build? I already tried with <IncludeAssets>all</IncludeAssets> but this only copies the dlls to output folder in some cases (e. g. rebuild project). But if I run the Azure Function debugger, the dlls are getting deleted again from output folder.

Copy local does not exist for package references:

Are you just building your project, or also publishing? – Maarten Nov 17 '21 at 13:09 — Maarten, Nov 17 '21 at 13:09
The Azure Function will also get published – MatterOfFact Nov 17 '21 at 13:11 — MatterOfFact, Nov 17 '21 at 13:11

score 1 · Answer 1 · answered Aug 31 '22 at 06:05

1

This works for me: <CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies>

Explanation: https://www.koskila.net/how-to-copy-dependent-assemblies-to-bin-folder-on-build/

answered Aug 31 '22 at 06:05

Lech Klimczak

11
3

How to force nuget package reference dlls to be copied to output directory?

1 Answers1