These pages cover Deployment Manager 1, which is not the latest version. Help for other versions is also available.

Skip to end of metadata
Go to start of metadata

To create application packages and publish them to a package feed, you can use the RgPublish.exe command line interface.

Databases

Icon

For information about creating database packages, see Creating and publishing database packages.

To download RgPublish.exe:

  1. In the web interface footer, click Deployment Manager tools:


  2. Under RgPublish.exe, click Download:

If you installed Deployment Manager to the default location, you can find RgPublish.exe in:

C:\Program Files (x86)\Red Gate\Deployment Manager\Tools

.NET Framework 4.0

Icon

Machines running RgPublish.exe require Microsoft .NET Framework 4.0. You can download the framework here.

Example: packaging and publishing a directory

In the following example:

  • the required files for the application we want to package are in C:\Source Code\My Web App\

    Icon
     For information about what packages should contain, and how to structure the directory you want to publish, see Working with packages.
  • we want to publish to our Deployment Manager package feed at http://localhost:8080/nuget/

To publish the directory, at the command prompt, we navigate to the location of RgPublish.exe and run:

This creates a package MyWebApp-1.0.nupkg, and pushes it to the package feed. You can now use Deployment Manager to deploy this package.

Example: packaging and publishing from a .nuspec file

In the following example:

  • the package.nuspec file describes the package we want to create

     Click to view the .nuspec file used in this example
    package.nuspec
    Icon

    For information about .nuspec files, see Nuspec reference (NuGet documentation)

  • the file paths defined in package.nuspec are relative to the base directory C:/Source Code/
  • we want to publish to a package feed at http://server:80/nuget, using the feed API key apikey1

To publish the package, at the command prompt, we navigate to the location of RgPublish.exe and run:

This creates a package Widget_Shop-1.0.0.nupkg, and pushes it to the package feed. You can now use Deployment Manager to deploy this package.

Syntax

Source

/source=<path>

Alias: /s

Path to a directory to publish, or a .nuspec file. For example:

or

Package details

You can specify details of the package using the following commands:

/packageid=<package name>

Alias: /id

Name of the package. For example:

If you don’t specify /packageid (or <id> in a .nuspec file), the directory name is used as the package name.

/version=<version number>

Alias: /v or /packageversion

Version number for the package. For example:

/description=<description>

A description of the package contents. For example:

If you don’t specify /description (or <description> in a .nuspec file), Published by Red Gate Publishing Tool is used as the description.

/author=<author name>

Author of the package. For example:

If you don’t specify /author (or <authors> in a .nuspec file), the current Windows user is used as the author name.

/basedir=<directory path>

Base directory where files defined in a .nuspec file are located (the directory against which paths in <files> are resolved). For example:

If the source is a .nuspec file and you don’t specify /basedir, the directory where the .nuspec file is located is used as the base directory.

Publishing to a directory

By default, packages are published to the working directory. You publish the package to a different directory using the following commands:

/target=<directory path>

Alias: /t

Path to a directory to publish to. For example:

/overwrite

Overwrites an existing package with the same name and version number.

Icon

If a package with the same name and version as you want to publish exists in the target directory and you don't specify /overwrite, package publishing will fail.

Publishing to a package feed

You can publish the package to a package feed using the following commands:

/target=feed:<package feed URL>

Alias: /t

URL of a package feed to publish to. For example:

If you publish to a package feed that requires an API key, specify:

/apikey=<feed API key>

API key for the package feed to publish to. For example:

  • No labels