ASP.NET Core is fast becoming the de-facto web framework in .NET. Compared to earlier versions of ASP.NET, it contains many changes to how applications are built, and how they are run.
If you are new to ASP.NET Core you can start with the Tutorial: Get Started ASP.Net Core tutorial.
Publishing and packing the website
When your application is ready, it needs to be published:
# Publish the application to a folder
dotnet publish source/MyApp.Web --output published-app --configuration Release
When your application has been published you need to package it:
# Package the folder into a ZIP
octo pack --id MyApp.Web --version 1.0.0 --basePath published-app
For more information about packaging applications see Creating packages using the Octopus CLI.
If you are using the built-in repository you can create a zip file.
When you have your generated nupkg or zip file it needs to be pushed to a repository.
If you are using TeamCity, you can use the new TeamCity plugin for dotnet commands.
OctoPack and .NET Core OctoPack is not compatible with .NET Core applications. If you want to package .NET Core applications see create packages with the Octopus CLI.
Deployment
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 .NET CLR Version is set to No Managed Code.
Antiforgery cookie
The .AspNetCore.Antiforgery cookie created by ASP.NET Core uses the application path to generate its hash. By default Octopus will deploy to a new path every time, which causes a new cookie to be set every deploy. This results in many unneeded cookies in the browser. See this blog post for more details. To change this behavior, set the Antiforgery token in your startup.cs like this:
public void ConfigureServices(IServiceCollection services)
{
services.AddAntiforgery(opts => opts.CookieName = "AntiForgery.MyAppName");
}
Cookie authentication in ASP.NET Core 2
Similar to antiforgery cookies, cookie authentication in ASP.NET Core 2 uses Microsoft’s data protection API (DPAPI) which can use the application path to isolates applications from one another. This can cause older cookies to simply not work. To change this behavior, you need to set the application name in your startup.cs like this:
public void ConfigureServices(IServiceCollection services)
{
services.AddDataProtection().SetApplicationName("my application");
}
Configuration
Refer to structured configuration variables on how to setup configuration.
Learn more
- Generate an Octopus guide for ASP.NET Core and the rest of your CI/CD pipeline.
Help us continuously improve
Please let us know if you have any feedback about this page.
Page updated on Sunday, January 1, 2023