This documentation is now out of date. As of the 1.0.0-rc2 release, ASP.NET Core uses the .NET CLI. For more information on the CLI visit https://docs.microsoft.com/en-us/dotnet/articles/core/tools/index
The DNX Utility (dnu) tool is responsible for all operations involved with packages in your application.
Restore (dnu restore)
The restore command will look at the dependencies of your application and download them, adding them to your apps packages directory. It downloads the entire graph of dependencies, even though you only explicitly declare the top level things that you directly depend on.
Install (dnu install <package id>)
The install command will download the given package and add it to your application.
Publish (dnu publish)
The publish command will package your application into a self-contained directory that can be launched. It will create the following directory structure:
- output/
- output/packages
- output/appName
- output/commandName.cmd
The packages directory contains all the packages your application needs to run.
The appName directory will contain all of your applications code, if you have project references they will appear as their own directory with code at this level as well.
The publish command will also hoist any commands from your project.json file into batch files. Running any of these commands is the same as running dnx <command>.
https://github.com/aspnet/Home/wiki/Dependency-Resolution
Pack (dnu pack)
Build NuGet packages for the project in given directory
Build (dnu build)
Produce assemblies for the project in given directory
Install (dnu install <packageId>)
Install the given dependency
Packages
Commands related to managing local and remote packages folders
List (dnu list)
Print the dependencies of a given project
Commands
Commands related to managing application commands (add, remove)
Wrap
Wrap a csproj into a project.json, which can be referenced by project.json files
Use "dnu help [command]" for more information about a command.