Скачать или смотреть Change Identity Routing in ASP.NET Core 3.1 from Identity/Account/Register to /Register

Learn how to easily modify the routing for identity actions in ASP.NET Core 3.1, specifically changing default paths for registration and login to a more user-friendly format.
---
This video is based on the question https://stackoverflow.com/q/67822917/ asked by the user 'Reza Shakeri' ( https://stackoverflow.com/u/13175549/ ) and on the answer https://stackoverflow.com/a/67831941/ provided by the user 'Yinqiu' ( https://stackoverflow.com/u/13973037/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: change identity routing in asp.net core 3.1 from Identity/Account/Register to /Register

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Changing Identity Routing in ASP.NET Core 3.1

In web development, routing is a critical aspect that determines how users interact with your application. When working with ASP.NET Core 3.1, you might encounter the default routing setup for identity actions such as registration and login. By default, these actions are mapped to specific routes like Identity/Account/Register and Identity/Account/Login. However, many developers prefer more user-friendly URLs like /Register and /Login. If you're one of them, this guide will show you how to achieve that with a simple adjustment to your code.

Problem Statement

As a developer working with ASP.NET Core 3.1, you might wish to customize the default routing framework for identity actions in your application. The existing routing to Identity/Account/Register can be cumbersome and not as intuitive for users. Changing this to simpler paths, such as /Register, will enhance the user experience and make your web application feel more cohesive.

The Solution: Modifying the Routing Framework

To change the identity routing from Identity/Account/Register to /Register, follow the steps outlined below:

Step 1: Locate the Registration View

Open your ASP.NET Core 3.1 project in your preferred code editor.

Navigate to the Identity folder.

Inside that folder, locate the subfolder Account.

Find the file Register.cshtml, which contains the registration page for your application.

Step 2: Update the Routing Directive

Next, you will need to modify the routing definition in the Register.cshtml file. Here's how to do it:

Open Register.cshtml.

At the very top of the file, you will find a directive that looks like this:

[[See Video to Reveal this Text or Code Snippet]]

Change this directive to specify the new route by updating it to:

[[See Video to Reveal this Text or Code Snippet]]

Step 3: Replicate for Other Routes

If you also want to change the login route from Identity/Account/Login to /Login, you can similarly navigate to Login.cshtml in the same Account folder and make a similar adjustment:

Open Login.cshtml.

Change the routing directive to:

[[See Video to Reveal this Text or Code Snippet]]

Step 4: Verify Your Changes

Save your changes in both Register.cshtml and Login.cshtml.

Run your application and test the new routes by navigating to /Register and /Login to ensure they work correctly and render the intended pages.

Conclusion

Customizing the routing for identity actions in ASP.NET Core 3.1 is a straightforward process that can significantly improve the usability of your web application. By following the steps outlined in this guide, you're not only creating a more user-friendly navigation experience but also enhancing the overall professionalism of your project. Always remember to test your changes in a development environment before pushing them to production.

If you have any questions or need further assistance, feel free to reach out in the comments below! Happy coding!