andrea-chiarelli

I have over 20 years of experience as a software engineer and technical author. Throughout my career, I've used several programming languages and technologies for the projects I was involved in, ranging from C# to JavaScript, ASP.NET to Node.js, Angular to React, SOAP to REST APIs, etc.

In the last few years, I've been focusing on simplifying the developer experience with Identity and related topics, especially in the .NET ecosystem.

Principal Developer Advocate

Andrea Chiarelli

A new version of the Auth0 Templates for .NET package has been released: discover the new powerful features.

In May, we [announced the release of Auth0 Templates for .NET](https://auth0.com/blog/introducing-auth0-templates-for-dotnet/), a NuGet package that allows .NET developers to scaffold a new project with Auth0 embedded. Today, we are announcing the release of a new powerful version of the package: [Auth0 Templates for .NET 2.1](https://www.nuget.org/packages/Auth0.Templates). 🎉

Go to your terminal window and install the new package by running the following command:

```bash
dotnet new install Auth0.Templates
```

> ⚠️ If you already have a previous version of the package installed on your machine, please uninstall it using the following command before installing the new package:
>
> ```bash
> dotnet new uninstall Auth0.Templates
> ```
>
> 

Let's explore what's new and how you can now create **a working application with Auth0 authentication in less than a minute!**

## Auth0 CLI integration

The most prominent feature introduced in this new release is the integration with the [Auth0 CLI](https://github.com/auth0/auth0-cli), the command line tool that allows you to manage your Auth0 tenants and your application registration from your terminal window.

> 📖 If you are new to the Auth0 CLI, take a look at [the Auth0 CLI Basics Lab](https://developer.auth0.com/resources/labs/tools/auth0-cli-basics) to learn how to use it.

If you have the Auth0 CLI installed on your machine and are already logged in to your Auth0 tenant, you can have your new application automatically registered. Let's do an example to better explain.

### Self-Registration in .NET CLI

Suppose you want to create a Blazor Server application with Auth0 authentication embedded. You can start by running the following command in a terminal window:

```bash
dotnet new auth0blazorserver -o MyBlazorServerApp
```

This command uses the `auth0blazorserver` template to create a Blazor Server application in the `MyBlazorServerApp` folder.

After launching the command, you will see a message similar to the following:

```bash
The template "Auth0 Blazor Server App" was created successfully.

Processing post-creation actions...

Template is configured to run the following action:
Actual command: register-with-auth0.cmd 
Do you want to run this action [Y(yes)|N(no)]?
```

With this message, the template engine asks if you want to register the newly created application with Auth0.

Once you confirm, the new Blazor application will be registered on your current Auth0 tenant. You will see the registration data onscreen for documentation purposes only, as you don't need to configure it manually. In fact, your new application will be automatically configured. All you need to do is run your Blazor application with `dotnet run`!

As you can see, using the integration with the Auth0 CLI allows you to have **an application up and running in less than a minute!**

Of course, you can still pass the configuration options on the command line in case you don't have the Auth0 CLI installed or if you have already registered the application with Auth0. See the [specific options for each template](https://github.com/auth0/auth0-dotnet-templates#usage) for more details.

### Auth0 registration in Visual Studio

If you are using the templates with Visual Studio, you can't leverage the self-registering feature. This is not a limitation of the template, but a restriction imposed by Visual Studio (see [this issue](https://github.com/dotnet/templating/issues/4575) for context).

However, you can run the registration action manually. So, assuming you want to create your Blazor Server application with Visual Studio, select the Auth0 Blazor Server App template as shown in the following picture:

![Auth0 Blazor Server template in Visual Studio](https://images.ctfassets.net/23aumh6u8s0i/4vIKOhrrozhmSDMkYPsEUr/5bd66766af25db726fb3aca5c4d731ab/auth0-blazorserver-app-vs.png)

Then, accept the default values proposed by the template configuration window and create the project.

After the project is created, go to the newly created application and run the following command:

```bash
./register-with-auth0.cmd
```

This command will automatically register your Blazor Server application with Auth0 and configure your application.

> Note: On MacOS you must enable the script to execute. Run the following command before launching the automatic registration:
>
> ```bash
> chmod +x register-with-auth0.cmd
> ```

## .NET 8 Support

The new release of Auth0 Templates for .NET supports .NET 8 by default for most templates. When you use the `dotnet new` command without specifying a framework version, you will get a .NET project with .NET 8 as the target framework. This is also the default .NET version when you are using Visual Studio, as shown below:

![Auth0 Template for ASP.NET Core MVC targeting .NET 8](https://images.ctfassets.net/23aumh6u8s0i/1mnYGKi2t006MED0sC2raQ/902bd9cb7b94be9e4b0d4c6c14b9d3ea/auth0-mvc-app-vs-options.png)

Blazor templates do not currently support .NET 8, but they still target .NET 7. The reason for this choice depends on the new .NET 8 Blazor model, which provides a more fluid approach between the Server and the WebAssembly hosting models. Currently, there are no official guidelines on how to integrate OpenID Connect with the new Blazor model. If you are interested in this topic, you can follow [this thread in the Auth0 Community forum](https://community.auth0.com/t/net-8-0-blazor/119691) to stay updated.

<include src="ebook-ads/dotnetIdentity" />

## Minimal API Template

The [Auth0 Templates for .NET package](https://www.nuget.org/packages/Auth0.Templates/) contains four templates since its first release:

- ASP.NET Core MVC
- ASP.NET Core Web API
- Blazor Server
- Blazor WebAssembly (ASP.NET Core hosted)

This new release adds a new template for [ASP.NET Core minimal API](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/minimal-apis). To use this template, add the `--minimal` option to the `dotnet new auth0webapi` command, as shown in the following example:

```bash
dotnet new auth0webapi -o MyWebAPI --minimal
```

This command creates a minimal API project in the `MyWebAPI` folder, and if you have the .NET CLI installed on your machine, it also registers it with Auth0.

In Visual Studio, you can simply select the *Use minimal API* checkbox as shown in the following picture:

![Options for the Auth0 ASP.NET Core Web API template in Visual Studio](https://images.ctfassets.net/23aumh6u8s0i/30Wl7yaOdnuWBhmdbRZa3v/259aa7ca9bb215da9fba8e62bfee8d87/auth0-webapi-app-vs-options.png)

## Looking Ahead

We hope that these new features will help .NET developers set up their new applications with Auth0 more easily than before. Our goal for the next release is to include a template for the missing Blazor model and add templates for other .NET application types.

Your feedback is valuable. If you experience a problem or have a request, please [open an issue](https://github.com/auth0/auth0-dotnet-templates/issues/new/choose) on the project's GitHub repository.

Remember that [Auth0 Templates for .NET](https://github.com/auth0/auth0-dotnet-templates) is an open source project, so your contribution is welcome! If you think you can help, check out [our contribution policy](https://github.com/auth0/auth0-dotnet-templates/tree/main#contributing) and get involved.



Auth0 Templates for .NET: A New Powerful Version Released

Kevin Lillybridge

I’ve been at Auth0 since 2020. I am the Group Product Manager for our SDK and developer tooling products. I have a passion for developer experience and love working with developers like yourself and learning about all the amazing products you’re building! When I’m not doing that, I enjoy spending time with my family, biking, skiing, and experimenting with the latest cookbook.

Group Product Manager

We’re thrilled to announce the launch of Auth0 CLI v1, which includes support for improved authentication processes, the new 'api' command, and much more.

For developers unfamiliar with the Auth0 CLI, it is a powerful tool designed to streamline and enhance your Auth0 development experience. The CLI empowers you to manage your Auth0 tenants effortlessly from the command line and automate tasks such as creating users, assigning roles, updating applications, and accessing unique features tailored to streamline your Auth0 integration process.

This article will highlight some of the most significant changes, but for a comprehensive overview and guidance on how to transition your current project to the new Auth0 CLI, we recommend following the official [v1 Migration Guide](https://github.com/auth0/auth0-cli/blob/v1.0.0/MIGRATION_GUIDE.md) and [Release Notes](https://github.com/auth0/auth0-cli/releases/tag/v1.0.0) on GitHub.

## The Journey to Auth0 CLI v1

The Auth0 CLI has come a long way since its humble beginnings during a hackathon over two years ago. Initially labeled as an experimental build, Auth0 CLI has received modest updates and feature enhancements along the way. Thanks to the continuous feedback and contributions from our developer community, we have been able to refine and expand its feature set, making the CLI a valuable tool for Auth0 developers.

The decision to transition from an experimental build to an officially supported General Availability (GA) build is a testament to our commitment to the Auth0 CLI and its continued development. This significant milestone reflects our confidence in the CLI's stability, reliability, and ability to cater to a diverse range of developer needs. By moving to GA, we're signaling our full support for Auth0 CLI and ensuring that devs can trust and rely on it as a core part of their workflow.

## What's New in Auth0 CLI v1

Let's look at some of the new updates in Auth0 CLI v1! This latest version is packed with new features and improvements to streamline your Auth0 development experience and boost efficiency. In this section, we'll dive into some of the most noteworthy additions and enhancements you can expect in Auth0 CLI v1.

### Improved authentication process

With Auth0 CLI v1, we've redesigned the interactive prompts at login to offer a seamless experience for authenticating as a user or as a machine for automating your backend services. This flexibility accommodates different types of developer workflows and situations, such as automating tasks or integrating with third-party services, making it simpler and more convenient for a wide range of users to get started with Auth0 CLI. Take a look at the improved authentication flow below to see just how fast it is to start using Auth0 CLI:

![Auth0 CLI authentication process](https://images.ctfassets.net/23aumh6u8s0i/3hwMPj6ZTc45CNUQkxY24L/5d5edb2e1b1f2bb913ea097adfa2e4e7/auth0-cli-authentication.gif)

### API command for authenticated Management API requests

The new `api` command enables you to make authenticated HTTP requests to the Management API directly, ensuring feature parity with our other development tools. This powerful addition provides a convenient and efficient way to access the Management API and further bridges the gap between the Auth0 CLI and any available Management API endpoint, making your workflow even more streamlined and cohesive. The animation below shows you just how easy it is to extend any Management API endpoint with Auth0 CLI:

![Auth0 CLI Management API](https://images.ctfassets.net/23aumh6u8s0i/7zEwdFMaA0XIzVwsuDKPLq/493f7a454494280599401a9066aa57da/auth0-cli-management-api.gif)

### Streamlined and expanded feature set

Auth0 CLI v1 is packed with numerous enhancements and bug fixes, offering developers a dependable and adaptable solution. These refinements increase the CLI's reliability, reflecting our unwavering dedication to continuously improve the tool in response to feedback from our growing developer community.

Boasting more than seventy new features, enhancements, and bug fixes, Auth0 CLI equips developers with unique features designed to optimize the Auth0 development experience, such as:

- Live tailing tenant logs
- Visualizing Universal Login modifications with Storybook and hot reloading
- Generating access tokens on demand
- Downloading, bootstrapping quickstarts

For a full list of changes, please refer to our [Release Notes](https://github.com/auth0/auth0-cli/releases/tag/v1.0.0) on GitHub.

![Register a new app with Auth0 CLI](https://images.ctfassets.net/23aumh6u8s0i/5gT494hRmVVE8bp42JdOjZ/097f8f915179e33924ff502a7ab6bd84/auth0-cli-app-registration.gif)

## Getting Started with Auth0 CLI v1

To get started with Auth0 CLI v1, follow these steps:

1. Install the CLI by following the instructions specific to your operating system on [GitHub](https://github.com/auth0/auth0-cli#installation).
2. Authenticate using `auth0 login` and follow the interactive prompt.

Thats it! Once you're authenticated, explore the available commands and features with `auth0 --help` or refer to the [documentation](https://github.com/auth0/auth0-cli) for a complete guide.

Note, if you are coming from a previous version of Auth0 CLI, please refer to the [v1 migration guide](https://github.com/auth0/auth0-cli/blob/v1.0.0-beta.3/MIGRATION_GUIDE.md), as this release includes breaking changes.

## Your Feedback Matters

Your feedback plays a crucial role in the ongoing improvement of Auth0 CLI. We encourage you to report bugs, suggest features, and share your thoughts through [GitHub issues](https://github.com/auth0/auth0-cli/issues). While v1 is a significant step forward, we have more plans for Auth0 CLI and we invite you to join us in this exciting journey and contribute to its future.

## Summary

Auth0 CLI v1 marks a new chapter in the Auth0 development experience. With its enhanced feature set and stability, it can become a useful tool in your Auth0 toolkit. We invite you to try it out and share your feedback to help us make the Auth0 CLI even better. Be sure to visit the [Auth0 CLI GitHub repository](https://github.com/auth0/auth0-cli) to stay informed on the latest developments and join the growing community of Auth0 CLI users.

"auth0-cli"