Great question! nopCommerce relies on its SEO-friendly URL system (powered by the UrlRecord table and custom routing logic) to map human-readable slugs like desktops to the corresponding numeric categoryId without needing it in the URL. Here's a step-by-step breakdown:

1. Custom Routing Configuration #

nopCommerce registers custom routes in its startup code that prioritize SEO-friendly URLs over default ASP.NET Core routing patterns. A simplified version of the route rule for category pages looks like this:

routes.MapRoute(
    name: "Category",
    url: "{SeName}",
    defaults: new { controller = "Catalog", action = "Category" },
    constraints: new { seNameConstraint = new SeNameRouteConstraint() }
);

The SeNameRouteConstraint is a custom constraint that validates if the SeName value (e.g., desktops) exists in the UrlRecord database table.

2. Slug-to-Entity Mapping via the UrlRecord Table #

When you visit /desktops, the system first queries the UrlRecord table to find a matching record where:

• SeName = 'desktops'
• EntityName = 'Category' (since this is a category page)

This record stores the corresponding EntityId — which is exactly the categoryId your Category action expects.

3. Parameter Binding & Route Resolution #

Once the categoryId is retrieved from the UrlRecord table, nopCommerce's routing system injects this value directly into the categoryId parameter of your CatalogController.Category action.

For the CatalogPagingFilteringModel parameter, ASP.NET Core's default model binding takes over: it populates the model from query string parameters (if present) or uses default values if none are provided.

4. Behind-the-Scenes Code Flow #

Here's a simplified look at the logic tying it all together:

• The SeNameRouteConstraint uses IUrlRecordService to call GetBySeName(seName) and verify the slug is valid.
• If a valid record is found, the system adds the categoryId (from UrlRecord.EntityId) to the route data.
• When the request reaches the Category action, ASP.NET Core binds the route data's categoryId value to the action's parameter.

So even though the URL doesn't explicitly show categoryId, nopCommerce's custom routing and slug resolution handle mapping the friendly URL to the numeric ID your action needs.

内容的提问来源于stack exchange，提问作者TheWebGuy