Umbraco .NET Core

    This article is intended for keeping an overview of all the information, official as well as unofficial, currently available on the upcoming release of Umbraco .Net Core.

    We have created a separate repository for articles and tutorials for Umbraco on .NET Core. Please keep in mind, that this is still a work in progress.

    Are you aware of some information about Umbraco .Net Core that isn't already added to this list? Please feel free to submit a Pull Request by using the Edit this page button at the top of this article.

    In this article you will find detailed instructions on how to try out and test the current alpha version of Umbraco .Net Core. You will also find a list of relevant links to official as well as unofficial resources on the upcoming release.

    News and updates from Umbraco HQ

    In this section you will find links to news and updates from the .Net Core team at Umbraco HQ, as well as from the UniCore community team.

    Blog posts

    Other resources

    Community resources

    In this section you will find a list of Umbraco .Net Core resources provided by the Umbraco Community.

    Community blog posts


    Umbraco .NET Core Alpha

    As of September 3rd 2020 it is possible to try out and test the latest alpha release of Umbraco .Net Core.

    Since March 24th 2021, the fourth alpha release has been available.

    More details on the alpha can be found in the alpha release blog post.

    As this is an alpha release, bugs and minor issues are to be expected.

    You can find a list of known issues in the release blog post and see already reported issues on the Issue tracker.

    Found a bug that isn't already reported? Please report it on the GitHub tracker with a title prefixed with “NetCore:”.

    To get started, follow the steps outlined below.

    Known issues and mising parts in current Alpha release

    • Restarts during install

      • When the Umbraco solution is installed, a restart is required. Right now we need to use IIS/IIS express to handle the next request and start the process again. Sometimes this fails and you need to start the process again
    • Members are still an area with lots of missing functionality

    • Mac/Linux + Examine/Lucene issue as that assembly still is built for .NET Framework.

    • Static events

      • The codebase still has some static events that are not migrated yet. Feel free to pick up some of them and help to migrate them. If you are a package developer and need to use some of the events that are not migrated yet, please reach out and tell us which you want us to prioritize.
    • File system abstractions

      • The current filesystem abstractions are expected to be changed before the final release. If you are a package developer, and your package mainly extends the file systems, we recommend that you wait for a later release before you start migrating that package.


    • .Net 5 SDK
    • SQL connection string (MS SQL Server/Azure), unless you want to install using SQL CE (Compact Edition)

    Steps to install the Umbraco dotnet new template

    1. Use a command prompt of your choice to insert this custom NuGet feed:

      dotnet nuget add source "" -n "Umbraco Prereleases"
    2. Install the new Umbraco dotnet template:

      dotnet new -i Umbraco.Templates::9.0.0-alpha004

    Steps to update the template from earlier alpha versions

    If you have already installed the Umbraco dotnet new template, you will need ensure it is up-to-date

    1. Use a command prompt of your choice to update the dotnet new templates

      dotnet new -i Umbraco.Templates::9.0.0-alpha004

    Steps to create an Umbraco solution using the dotnet new template

    1. Create a new empty Umbraco solution using MS SQL Azure/Server:

      dotnet new umbraco -n MyCustomUmbracoSolution

      Or if you prefer to using SQL CE:

      dotnet new umbraco -n MyCustomUmbracoSolution -ce

    You will now have a new project with the name MyCustomUmbracoSolution, or whichever name you chose.

    The new project can be opened and run using your favorite IDE or you can continue to use the CLI commands.

    Steps to build and run

    The following steps, will continue using CLI based on the steps above.

    1. Navigate to the newly created project folder:

      cd MyCustomUmbracoSolution
    2. Build and run the new Umbraco .Net Core project:

      dotnet build
      dotnet run

    The project is now running on the Kestrel server and is available on the default ports: http://localhost:5000 and https://localhost:5001.

    The next step is to run through the Umbraco CMS installation. If you chose to use MS SQL Server/Azure you will need to add your connection string during this setup process.

    Once the installation process is complete you might need to manually restart the application in order to start the application again and get access to the Umbraco backoffice.

    .NET Core Nightly Builds

    To get the latest nightly builds - the latest version of the Umbraco dotnet template, you will need to add another NuGet source.

    1. Use a command prompt of your choice to insert this custom NuGet feed:
    dotnet nuget add source "" -n "Umbraco Nightly"
    1. Install the new Umbraco dotnet template
      dotnet new -i Umbraco.Templates::9.0.0-*

    In order to get the latest template from the new source, you will need to use a wildcard symbol like shown above.

    Now you can continue in the same way as if you were using the Alpha version

    Package development

    Since Alpha 4, we have added a new template to in Umbraco.Templates package which is targeting packages.

    To use the new template write:

    dotnet new umbracopackage -n MyCustomUmbracoPackage

    This generates an empty package with an empty package.manifest. But more importantly it also contains a build/MyCustomUmbracoPackage.targets file.

    This file will be included in the NuGet package when using dotnet pack.

    The file contains an msbuild target that is executed on build when a project has a dependency to this package. It copies the app_plugin folder into the project. This is required for having Umbraco packages as NuGet packages.

    Furthermore, we introduced a new flag on the regular dotnet new umbraco template. You can now write:

    dotnet new umbraco -n MyCustomUmbracoSolution -p MyCustomUmbracoPackage

    This new -p indicates that the solution is a test-site of the package MyCustomUmbracoPackage. It will add a project dependency to MyCustomUmbracoPackage and import the target file from that project. So when you build the new solution, it will also copy the App_Plugins folder from the package project into the solution. In the same way, as if it was a NuGet reference.

    Full example

    The following shot example shows how to use the templates in combination

    dotnet new umbracopackage -n MyCustomUmbracoPackage
    dotnet new umbraco -n MyCustomUmbracoPackage.Testsite -p MyCustomUmbracoPackage
    cd MyCustomUmbracoPackage.Testsite
    dotnet build