dose using the App.Map() considerd endpoin or a middlewear?

if i used below dose this considered a middlewear or a endpoint ,and dose middlewears only created using Use() and Run()

app.Map("/" ,async context => await context.Response.WriteAsync("Hello World") )

and alos i want to ask why dose the Use in this code invoked before the Map()

app.UseRouting();

app.Use(async (context, next) =>
{
    await context.Response.WriteAsync(MyCustomKeyValue + '\n');
    await next();
    await context.Response.WriteAsync("The Value Appers there" + '\n');
});

app.Map("/", async (context) =>
{
    await context.Response.WriteAsync("From Route /" + '\n');
});

Hi Mina,

In your first question:

app.Map("/", async context => await context.Response.WriteAsync("Hello World"));

This is considered an endpoint. Map defines a specific route and associates it with a request delegate, which directly handles requests that match the route pattern. This behavior makes Map part of endpoint routing, rather than middleware.

In your second question:

Why is Use invoked before Map?

Middleware (app.Use) is part of the request processing pipeline, and it executes in the order it's added. Middleware is typically added using Use(), Map(), or Run(). Middlewares can intercept the request and either handle it or pass it along to the next middleware using next(). The app.UseRouting() middleware sets up routing but doesn't yet execute the matched endpoint.
Endpoint (app.Map) defines a specific route and request handler but isn't middleware. It's executed after all middleware has run and when the UseEndpoints() middleware is invoked (though not visible here, it's usually added later). Hence, the middleware defined with Use() runs first.

Middleware and Use/Run:

Middlewares are typically created using Use(), which chains to the next middleware, or Run(), which short-circuits the pipeline (i.e., no next()).
- app.Use() allows the middleware to pass control to the next one in line (await next()).
- app.Run() terminates the pipeline, so no further middleware is invoked.

So, the order in which middleware and routes are added is critical to how the request is processed. The Map endpoint here is invoked after the Use() middleware finishes.

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Aman Gupta2y ago
Accepted answer
Hi Mina,

In your first question:
```
app.Map("/", async context => await context.Response.WriteAsync("Hello World"));
```
This is considered an endpoint. Map defines a specific route and associates it with a request delegate, which directly handles requests that match the route pattern. This behavior makes Map part of endpoint routing, rather than middleware.

In your second question:

Why is Use invoked before Map?
- Middleware (app.Use) is part of the request processing pipeline, and it executes in the order it's added. Middleware is typically added using Use(), Map(), or Run(). Middlewares can intercept the request and either handle it or pass it along to the next middleware using next(). The app.UseRouting() middleware sets up routing but doesn't yet execute the matched endpoint.
- Endpoint (app.Map) defines a specific route and request handler but isn't middleware. It's executed after all middleware has run and when the UseEndpoints() middleware is invoked (though not visible here, it's usually added later). Hence, the middleware defined with Use() runs first.
Middleware and Use/Run:
- Middlewares are typically created using Use(), which chains to the next middleware, or Run(), which short-circuits the pipeline (i.e., no next()).
  
  app.Use() allows the middleware to pass control to the next one in line (await next()).
  
  app.Run() terminates the pipeline, so no further middleware is invoked.
So, the order in which middleware and routes are added is critical to how the request is processed. The Map endpoint here is invoked after the Use() middleware finishes.
+3