Ben Foster • 3/19/2020

Resolving the current route name in ASP.NET Core 3.1

Read Original

This technical article explains how to resolve the current route name in ASP.NET Core 3.1 for API metrics tracking. It details the shift from ASP.NET Core 2.2's IRouteValuesAddressMetadata to 3.0+'s EndpointNameMetadata, providing code examples for a custom extension method to get the route name from HttpContext in middleware.

0 comments
#routing #middleware #Aspnet Core
Resolving the current route name in ASP.NET Core 3.1

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
The Beautiful Web
Jens Oliver Meiert • 2 votes
2
When your coding agent doesn’t understand your project, you’ll get junk
Benjamin Cane • 1 votes
3
LLM Use in the Python Source Code
Miguel Grinberg • 1 votes
4
Wagon’s algorithm in Python
John D. Cook • 1 votes
5
An example conversation with Claude Code
Dumm Zeuch • 1 votes