Скачать или смотреть Troubleshooting ASP.NET MVC 5 Routes: Using Friendly URLs Instead of GUIDs

Learn how to configure ASP.NET MVC 5 routes for friendly URLs instead of GUIDs and ensure your CRUD operations work seamlessly.
---
This video is based on the question https://stackoverflow.com/q/37711352/ asked by the user 'Archil Labadze' ( https://stackoverflow.com/u/4089212/ ) and on the answer https://stackoverflow.com/a/70364799/ provided by the user 'Archil Labadze' ( https://stackoverflow.com/u/4089212/ ) 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: MVC 5 Routes - Using URL string einstead GUID

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 3.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.
---
Troubleshooting ASP.NET MVC 5 Routes: Using Friendly URLs Instead of GUIDs

In the world of web development, making your URLs user-friendly is vital for SEO and user experience. Many developers are looking to implement custom URL strings rather than traditional GUID routes for their models. In this post, we will explore the challenges faced when manipulating routes in ASP.NET MVC 5, specifically focusing on converting GUIDs to friendly URLs.

The Problem

When building an application, you may want to allow users to access their profiles using a simple, readable URL instead of a complex GUID. For instance, instead of the default URL:

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

You might want something like:

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

However, while trying to achieve this, you may run into errors, such as encountering HTTP Error 400 - Bad Request. Let's break down both the routing setup and the controller actions that often lead to these errors.

The Initial Setup

Consider the model UserProfile which includes a UrlSeo property intended for friendly URLs. Here’s a look at the model:

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

The Initial Routing Configuration

Initially, the developer set up the following routes:

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

However, this configuration resulted in errors, particularly HTTP 400 errors when using string parameters.

The Solution

After researching and troubleshooting, the key point discovered was that the route was expecting a GUID as an id but was being passed a string instead. The successful approach involved modifying the controller method to accept a string parameter rather than a GUID.

Step 1: Modify Controller Action

Here's how you can change the Details action:

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

Step 2: Update the Routing Setup

In the routing setup, change the way URLs are processed:

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

Conclusion

By accepting a string in the Details action and adjusting the routing configurations accordingly, the application can now handle both friendly URLs and standard GUID routes.

This method not only helps maintain the simplicity and readability of your URLs but also ensures your CRUD operations continue to function properly without unexpected errors.

If you run into similar roadblocks while working with ASP.NET, always remember to check what type of data your actions expect and how your routes are configured.

Feel free to share your experiences or further questions related to routing in ASP.NET MVC 5!