Routing

I wrote about this back in the days of .NET Core 2.0. How to do this has changed in .NET 10.

In .NET Core Web Api it is not possible for the routing mechanism to distinguish between two action methods with different query string parameters. But with the help of an ActionMethodSelectorAttribute you can tell the methods apart.

Full source code available here. Routing in .NET Core Web Api (1.1 and 2) is a little different than in earlier versions. I’ve written about this a few times, you can find those posts here.

I have two other posts on multiple GET methods, one for ASP.NET 5 Web Api, and another for Web Api 2. Download full source code. A few months ago I wrote a post explaining how to create a controller with multiple GET methods.

I have two other posts on multiple GET methods, one for ASP.NET 5 Web Api, and another for Web Api 2. It seems that every version of Web API changes how it handles default routes or route prefixes or whatever the next name will be.

A simple example of how to create a Web Api controller with multiple get methods in ASP.NET 5.