What is "Pack" option useful for ?
It seems that it does the same thing as Build. The output is following
1>------ Build started: Project: KnockoutTest, Configuration: Debug Any CPU ------ 1>KnockoutTest -> C:\Users\path\bin\Debug\netcoreapp2.0\KnockoutTest.dll ========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
This is generally also what the “Pack” command does in the context menu in Visual Studio. Packing will usually involve building the project properly and then packing it into a . nupkg file. If you look at your project output, you should see a KnockoutTest.
The dotnet pack command builds the project and creates NuGet packages. The result of this command is a NuGet package (that is, a . nupkg file).
Solution Explorer is a special window that enables you to manage solutions, projects, and files. It provides a complete view of the files in a project, and it enables you to add or remove files and to organize files into subfolders.
The term “pack” comes from NuGet, where “packing” basically means that you create a NuGet package out of your project.
This is usually done using the NuGet command line, by calling nuget pack
.
With .NET SDK based projects, e.g. ASP.NET Core, this functionality is also available through dotnet pack
which makes the package creation process a bit simpler (by assuming many defaults, making this less customizable than nuget pack
).
This is generally also what the “Pack” command does in the context menu in Visual Studio. Packing will usually involve building the project properly and then packing it into a .nupkg
file. If you look at your project output, you should see a KnockoutTest.nupkg
file as well.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With