.\" Automatically generated by Pandoc 2.1.3
.\"
.TH "dotnet store command" "1" "" "" ".NET Core"
.hy
.SH dotnet store
.PP
.SH NAME
.PP
\f[C]dotnet\ store\f[] \- Stores the specified assemblies in the runtime package store.
.SH SYNOPSIS
.PP
\f[C]dotnet\ store\ \-m|\-\-manifest\ \-f|\-\-framework\ \-r|\-\-runtime\ \ [\-\-framework\-version]\ [\-h|\-\-help]\ [\-\-output]\ [\-\-skip\-optimization]\ [\-\-skip\-symbols]\ [\-v|\-\-verbosity]\ [\-\-working\-dir]\f[]
.SH DESCRIPTION
.PP
\f[C]dotnet\ store\f[] stores the specified assemblies in the runtime package store.
By default, assemblies are optimized for the target runtime and framework.
For more information, see the runtime package store topic.
.SS Required options
.PP
\f[C]\-f|\-\-framework\ <FRAMEWORK>\f[]
.PP
Specifies the target framework.
.PP
\f[C]\-m|\-\-manifest\ <PATH_TO_MANIFEST_FILE>\f[]
.PP
The \f[I]package store manifest file\f[] is an XML file that contains the list of packages to store.
The format of the manifest file is compatible with the \f[I]csproj\f[] format.
So, a \f[I]csproj\f[] project file that references the desired packages can be used with the \f[C]\-m|\-\-manifest\f[] option to store assemblies in the runtime package store.
To specify multiple manifest files, repeat the option and path for each file: \f[C]\-\-manifest\ packages1.csproj\ \-\-manifest\ packages2.csproj\f[].
.PP
\f[C]\-r|\-\-runtime\ <RUNTIME_IDENTIFIER>\f[]
.PP
The runtime identifier to target.
.SS Optional options
.PP
\f[C]\-\-framework\-version\ <FRAMEWORK_VERSION>\f[]
.PP
Specifies the .NET Core SDK version.
This option enables you to select a specific framework version beyond the framework specified by the \f[C]\-f|\-\-framework\f[] option.
.PP
\f[C]\-h|\-\-help\f[]
.PP
Shows help information.
.PP
\f[C]\-o|\-\-output\ <OUTPUT_DIRECTORY>\f[]
.PP
Specifies the path to the runtime package store.
If not specified, it defaults to the \f[I]store\f[] subdirectory of the user profile .NET Core installation directory.
.PP
\f[C]\-\-skip\-optimization\f[]
.PP
Skips the optimization phase.
.PP
\f[C]\-\-skip\-symbols\f[]
.PP
Skips symbol generation.
Currently, you can only generate symbols on Windows and Linux.
.PP
\f[C]\-v|\-\-verbosity\ <LEVEL>\f[]
.PP
Sets the verbosity level of the command.
Allowed values are \f[C]q[uiet]\f[], \f[C]m[inimal]\f[], \f[C]n[ormal]\f[], \f[C]d[etailed]\f[], and \f[C]diag[nostic]\f[].
.PP
\f[C]\-w|\-\-working\-dir\ <INTERMEDIATE_WORKING_DIRECTORY>\f[]
.PP
The working directory used by the command.
If not specified, it uses the \f[I]obj\f[] subdirectory of the current directory.
.SH EXAMPLES
.PP
Store the packages specified in the \f[I]packages.csproj\f[] project file for .NET Core 2.0.0:
.PP
\f[C]dotnet\ store\ \-\-manifest\ packages.csproj\ \-\-framework\-version\ 2.0.0\f[]
.PP
Store the packages specified in the \f[I]packages.csproj\f[] without optimization:
.PP
\f[C]dotnet\ store\ \-\-manifest\ packages.csproj\ \-\-skip\-optimization\f[]
.SS See also
.PP
Runtime package store
.SH AUTHORS
bleroy.