What is the difference between using Route and without in Web Api Controller?

Question

I have this code in Web Api controller in C#. One is with Route attribute and another is without.

    [HttpGet]
    [Route("GetReport")]
    public async Task<IActionResult> GetReport(){
      // code removed for brevity
    }

and another version is

    [HttpGet("GetReport")]
    public async Task<IActionResult> GetReport(){
      // code removed for brevity
    }

They both works the same, is it?

Answer 1

They both works the same, is it?

Yes, though you might prefer to just use the HttpGet("...") as it's neater to use one attribute instead of two. Personally I don't use Route, and I fully specify all routes in a HttpXxx, purely because finding the relevant code when some/page/url/blah is crashing, is a matter of doing Ctrl-F for the route as presented in the browser address bar (minus any parameter values). That's a lot harder to do if your route is broken up across RoutePrefix/Route