History

Bryan Thornbury 709f7b7d14 Enable Cross Publishing and add tests WIP WIP WIP Test out not publishing runtimeAssets WIP WiP x-publish update cross-publish-test Update Cross Publish tests remove --config from restore fix build update cross publish tests fix test compilation error test failure fix fix test failure update tests tracing fix desktop publishing do publish with no build, call build manually fix Make host publish optional, fix faux libraries? update Cross Publish test working try changing test to netcore.app fallback to host from current platform revert change to project.json to target Microsoft.NETCore.App fallback to compilation build output update kestrel standalone app project.json Make project tools command resolver test more self-contained. make Kestrel Standalone restore against N-1		2016-04-12 13:00:04 -07:00
..
Program.cs	Publish can skip Build	2016-03-30 19:24:43 -07:00
PublishCommand.cs	Enable Cross Publishing and add tests	2016-04-12 13:00:04 -07:00
README.md	Everything in the same project	2016-02-01 14:56:32 -08:00

README.md

% DOTNET-PUBLISH(1) % Zlatko Knezevic zlakne@microsoft.com % January 2016

NAME

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

SYNOPSIS

dotnet-publish [--framework]
[--runtime] [--output]
[--configuration]
[< 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 will contain the assemblies, the runtime as well as the executable version of the application. This directory can then be moved to a different machine and the application will be able to run regardless of existence of any other runtime.

The native dependencies of the runtime are not packaged with the application. This means that the target machine needs to have the native dependencies installed in order for the application to run.

OPTIONS

[project]

`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. `dotnet-publish` command also requires certain dependencies in the `project.json` to work. Namely the `Microsoft.NETCore.Runtime` package must be referenced as a dependency in order for the command to copy the runtime files as well as the application's files to the published location.

-f, --framework [FID]

Publish the application for a given framework identifier (FID). If not specified, FID is read from `project.json`. 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.

-r, --runtime [RID]

Publish the application for a given runtime. If the option is not specified, the command will default to the runtime for the current operationg system. Supported values for the option 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`