NuGet package dependencies and build/deploy servers

Question

We're using FluentMigrator (a NuGet package) on an ASP.net/MVC project to maintain database changes to our SQL Server.

What is the "correct" way to distribute a NuGet package with other build artifacts for usage during a deployment? Do I only need the "packages" folder?

I'm hoping for a response other than "use package manager and install the Nuget package on PROD".

I don't want to pull the package (from either local or non-local sources) during deployment, I want to include the correct package with my compiled code.

Answer 1

The correct way is to pull the package down before building the project, then assuming your project references the assembly such that Copy Local is true, it will be included in the build output, which should be stored as an artifact in your CI tool.

You definitely should not be doing anything related to NuGet beyond this point in your build/deployment process.