Uri Generation

Strongly typed URL generation for ASP.NET Core:

_uriGenerator.GetUriByExpression<InvoicesController>( httpContext, c => c.GetInvoice(2));

Features:

• Extracts action name, controller name, and route values from expression
• Delegates URL generation to LinkGenerator
• Supports ActionName, Area, NonAction, NonController, FromBody, FromForm, FromHeader and FromServices attributes
• Supports IFormFile, IFormFileCollection, IEnumerable<IFormFile>, CancellationToken and FormCollection types
• Supports Controller and Async suffixes
• Supports LinkOptions
• Supports bypassable caching

Attribute routing:

If multiple URL paths match an action in your controller:

[HttpGet("api/invoices/{id}", Name = "ApiGetInvoice")] [HttpGet("invoices/{id}", Name = "GetInvoice")] public InvoiceResource GetInvoice(int id)

you can specify an endpoint name to generate an endpoint-specific URL:

_uriGenerator.GetUriByExpression<InvoicesController>( httpContext, c => c.GetInvoice(2), "ApiGetInvoice"); _uriGenerator.GetUriByExpression<InvoicesController>( httpContext, c => c.GetInvoice(2), "GetInvoice");

To further improve on this, you can use classes such as Microsoft.Azure.Management.ResourceManager.Fluent.Core.ExpandableStringEnum instead of strings to define your endpoint names. That would require you to write a simple adapter class that takes a string from your class and passes it to UriGenerator.

Performance:

Extracting values from expression trees does introduce some overhead. To partially work around this problem, UriGeneration uses ASP.NET's CachedExpressionCompiler, so that equivalent route values' values' expression trees only have to be compiled once.

Additionally, it uses its internal Microsoft.Extensions.Caching.Memory.MemoryCache instance to cache extracted controller names, action names, and route values' keys within the scope of the application lifetime.

This means that, for example, on 2017 Surface Book 2 you are able to generate 100000 URLs in a second using a template like this: .