This page is for Octopus Deploy 3.0 and newer versions. You can view this page for Octopus 2.0

Skip to end of metadata
Go to start of metadata

ASP.NET Core is the future of ASP.NET, and it contains many changes to how applications are built, and how they are run.

Publishing and Packing the Website

Once you have a project up and running (see the getting started guide), it need to be published and packed

If you are using the built-in repository, you can create a zip file instead. The generated nupkg or zip file should then be then be pushed to a repository.

If you are using TeamCity, you can use the new TeamCity plugin for dotnet commands


ASP.NET Core applications can either run as a command line program with Kestrel, or under IIS (which also uses Kestrel - check out the book for details).


See the ASP.NET Core IIS documentation for instructions on setting up IIS for ASP.NET Core

When running under IIS, ensure the Relative home directory is specified as "wwwroot" for compatibility with IIS.




ASP.NET Core introduces a new JSON-based configuration file format. Octopus 3.3 introduced a new convention which can be used to update these JSON configuration files with Octopus variables 

For more information, see the section on the JSON Configuration Variables Feature.




  • No labels