History

Mihai Codoban 110b30ccdc Extract build from compile Build becomes the new compile. It decides which project to compile and how. It checks for incremental preconditions Compile's resonsibility is trimmed down to only knowing how to invoke the compiler on a project		2015-12-23 17:31:47 -08:00
..
Microsoft.DotNet.Tools.Publish.xproj	merge my spike on compile/publish/run and switch from PS1 to C#	2015-10-06 10:46:43 -07:00
Program.cs	Make dotnet-publish slightly more readable	2015-12-15 23:55:56 -08:00
project.json	rc2-23616 to hopefully resolve crossgen issues	2015-12-16 11:48:33 -08:00
PublishCommand.cs	Extract build from compile	2015-12-23 17:31:47 -08:00
README.md	Removing redundant bullet point	2015-12-03 19:13:18 +00:00

README.md

dotnet-publish

NAME

dotnet-publish

packs the application and all of its dependencies into a folder getting it ready for publishing

SYNOPSIS

dotnet-publish [options] [project]

DESCRIPTION

dotnet-publish will compile the application, read through its dependencies specified in project.json and publish the resulting set of files to a directory. This directory contains the assemblies, the runtime as well as the runnable version of the application. This directory can then be moved to a different machine and the application will be able to be ran regardless of existence of any other runtime.

dotnet-publish needs access to project.json to work. If it is not specified on invocation via [project], project.json in the current directory will be the default. If no project.json can be found, dotnet-publish will error out.

The command also requires information on the targeted framework and runtime, both of which can be specified on the command line. If the runtime is not specified, the command will default to the runtime for the current operating system. If the framework is not specified, the command will read the information from the project.json file. In case of no valid framework found, the command will error out. In case of multiple valid frameworks found, the command will publish for all valid frameworks.

Options

-f, --framework [FID]

Publish the application for a given framework identifier (FID). If not specified, FID is read from project.json.

-r, --runtime [RID]

Publish the application for a given runtime. Supported values for runtimes at this time are:

* ubuntu.14.04-x64
* win7-x64
* osx.10.10-x64

-o, --output

Specify the path where to place the directory. If not specified, will default to ./bin/[configuration]/[framework]/[runtime]/

-c, --configuration [Debug|Release]

Configuration to use when publishing. If not specified, will default to "Debug".

EXAMPLES

dotnet-publish

Publish the current application using the project.json framework and runtime for the current operating system.

dotnet-publish ~/projects/app1/project.json

Publish the application using the specified project.json; also use framework specified withing and runtime for the current operating system.

dotnet-publish --framework dnxcore50

Publish the current application using the dnxcore50 framework and runtime for the current operating system.

dotnet-publish --framework dnxcore50 --runtime osx.10.10-x64

Publish the current application using the dnxcore50 framework and runtime for OS X 10.10

SEE ALSO

dotnet-restore