Download the computed dependency graph.
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
|
paket restore [--help] [--force] [--only-referenced] [--touch-affected-refs] [--ignore-checks]
[--fail-on-checks] [--group <name>] [--project <path>] [--references-file <path>]
[--target-framework <framework>] [--output-path <path>]
OPTIONS:
--force, -f force download and reinstallation of all dependencies
--only-referenced only restore packages that are referenced by paket.references files
--touch-affected-refs touch project files referencing affected dependencies to help incremental
build tools detecting the change
--ignore-checks do not check if paket.dependencies and paket.lock are in sync
--fail-on-checks abort if any checks fail
--group, -g <name> restore dependencies of a single group
--project, -p <path> restore dependencies of a single project
--references-file <path>
restore packages from a paket.references file; may be repeated
--target-framework <framework>
restore only for the specified target framework
--output-path <path> Output path directory of MSBuild. When used in combination with the new
dotnet cli based sdk, paket will write supporting files (nuget.config,
paket.resolved) there
--silent, -s suppress console output
--verbose, -v print detailed information to the console
--log-file <path> print output to a file
--help display this list of options.
|
If you add the --verbose flag Paket will run in verbose mode and show detailed information.
With --log-file [path] you can trace the logged information into a file.
paket restore fails with an error if the paket.lock file
does not exist. No packages are downloaded in that case. Please see
paket install and paket update to
learn how to create the paket.lock file.
