Take advantage of the open source library Serilog to log your ASP.NET Core application’s data to SQL Server or another database target.

ASP.NET sees the session cookie and loads the session (or doesn't, and starts a new one). This is why people recommend serving static, unauthenticated resources like images from a separate domain.

You can take advantage of custom route constraints in ASP.NET Core to validate route values and avoid passing unwanted or unnecessary requests to action methods.

Sometimes I'm just plain lazy. Other times I don't want to have to spend hours debugging ASP code because of typos so I've found a way to help short cut some repetitive ASP coding tasks. The idea is ...