Q
Q-tec
Guest
Hello,
I have a .net standard library which is referencing onto multiple entity framework core packages via NuGet. However when I build it he only copies my own libaries into the output but not the required dependencies which have been added via NuGet.
I did not find an option (copy locally) like you have when you setup a real reference without that NuGet nonsense.
Is there a way to force him to copy references into into local folder? It's just a pain in the a** to search for the libs in C:\%User%\NuGet" and copy them manually into the output folder.
Furthermore I would like to ask if there is a way to teach NuGet to put the references into the solution folder instead of "C:\%User%\NuGet"?
I normally do not use NuGet but I know that a few years ago he did store everything solution related into the solution folder. I could not find anything in the settings and I did not find a solution in their "documentation".
Best regards
Dev86 Technical Blog
Continue reading...
I have a .net standard library which is referencing onto multiple entity framework core packages via NuGet. However when I build it he only copies my own libaries into the output but not the required dependencies which have been added via NuGet.
I did not find an option (copy locally) like you have when you setup a real reference without that NuGet nonsense.
Is there a way to force him to copy references into into local folder? It's just a pain in the a** to search for the libs in C:\%User%\NuGet" and copy them manually into the output folder.
Furthermore I would like to ask if there is a way to teach NuGet to put the references into the solution folder instead of "C:\%User%\NuGet"?
I normally do not use NuGet but I know that a few years ago he did store everything solution related into the solution folder. I could not find anything in the settings and I did not find a solution in their "documentation".
Best regards
Dev86 Technical Blog
Continue reading...