Typically with ASP.NET Core 3.1 when no specific authorization requirements are set all endpoints are publicly accessible. When you’re wo...
asp.net coreIf you have used slots in Vue, you know that it provides a clean way to vary content that is displayed in child components. For example, ...
VueJS Slots Scoped Slots JavaScriptWe’ve been using Swagger via Swashbuckle for some time with our ASP.NET Full Framework applications. As we’re moving toward ASP.NET Core ...
asp.net coreWe’ve spotted some strange behavior before with ASP.NET Core and JSON serialization/deserialization, and I eventually made it back to try...
asp.net coreWe’ve spotted some strange behavior before with ASP.NET Core and JSON serialization/deserialization, and I eventually made it back to try...
asp.net coreAs we create CSS components in our internal framework, we typically try to use little if no JS. Our tooltips should be no different. We...
UI/UX frontend CSS Responsive DesignImagine you’re using Elasticsearch with your strongly typed C# models and nameof(MyProperty) and wondering why it doesn’t work. Turns out...
.NETI have been working as a software developer for almost three years, the most common exception or bug I made is NullReferenceException -Sy...
.NET C#Testing is an important step we can take as developers to reduce bugs in our code, but testing seems to be one of the best practices that...
Vue.js Jest TestingLast week I attended the annual user experience conference Convey UX in Seattle, where 50 UX leaders from all over the world shared their...
UI/UX frontend conference conveyux2020 conveyuxWe run a number of web applications at Ritter Insurance Marketing. Our primary datastore for these applications is MSSQL / SQL Azure. Our...
SQLWe’ve been working through upgrading our core applications from ASP.NET full framework to ASP.NET Core. Over the years we’ve assembled an...
.NETConfigurationManager has long been used by .NET Framework developers prior to .NET Core to access things like app settings and connection...
.NETWe’ve had some internal discussion around the usage of RegexOptions.Compiled in .NET – how it works and when it’s appropriate to use it. ...
.NETDebugging web applications can be difficult sometimes. When debugging a failed HTTP GET request in Application Insights you have all of t...
.NETSupporting IE comes with challenges if you are using es6, and while babel helps greatly there is a few gotcheas. One of the main one is u...
JavaScript IE 11For a long time, we were dependent on the CSS frameworks of others – and we were quite happy. 😀 As our needs grew, we needed a framework...
Sass Dart SassAutofac is an inversion of control container for .NET. It allows developers to register items and then later use those registrations to i...
.NETWorking with dates can seem a little daunting sometimes. We need specific formatting, and hopefully we don’t have to deal with timezones ...
JavaScript Vue HTMLRead ASP.NET Core 2.2 First Look – Endpoint Routing and ASP.NET Core updates in .NET Core 3.0 Preview 2 to get a more-detailed picture on how routing is now exposed in relation to ASP.NET Core.
Routing has traditionally been a construct confined within the ASP.NET ecosystem. As long as your code executes within that construct, you can read route data. However, with the proliferation of middleware that run before and after ASP.NET, the desire/need for an app.-wide, exposed routing system increased.
using Microsoft.AspNetCore.Internal;
public class Startup
{
public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
app
.UseEndpointRouting() // Registering this prior to your middleware unlocks the ✨.
//.YourMiddleware()
.UseMvc();
}
}
using Microsoft.AspNetCore.Builder;
public class Startup
{
public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
app
.UseRouting() // Registering this prior to your middleware unlocks the ✨.
//.YourMiddleware()
.UseMvc();
}
}
Imagine you’re building a new blog engine… 🤔
💡 Maybe you want to pre-load a post via middleware so it’s available anywhere down the chain. This way, none of other middleware is concerned with how to retrieve the post and can instead focus on whatever it does to augment the response.
public class Post
{
public string Slug { get; set; }
public string Title { get; set; }
}
/// <summary>
/// We need a derivative class to support scenarios where we can't find a `Post`-record based on {slug}.
/// DI will throw an exception if we try to give it `null`.
/// </summary>
public class GenericPost : Post
{ }
@page "{slug}"
@model PostModel
<h1>@Model.Title</h1>
...
public class PostModel : BaseModel
{
public PostModel(Post post)
{
this.post = post;
}
public Post post { get; private set; }
public void OnGet()
{ }
}
public class PostMiddleware
{
public PostMiddleware(
RequestDelegate next,
IDatabase database)
)
{
this.next = next;
this.database = database;
}
private readonly IDatabase datbase;
private readonly RequestDelegate next;
public async Task InvokeAsync(HttpContext context)
{
var route = context.GetRouteData();
if (route.Values.TryGetValue("slug", out var routeSlug))
{
var slug = routeSlug.ToString();
var post = (await database.Fetch<Post>()).FirstOrDefault(x => x.Slug == slug);
if (post != null)
{
context.Items.Add(nameof(Post), post);
}
}
await next(context);
}
}
ℹ️ This could also be refactored into a separate extension-method.
public void ConfigureServices(IServiceCollection services)
{
services.AddScoped<Post>(serviceProvider =>
{
var accessor = serviceProvider.GetRequiredService<IHttpContextAccessor>();
if (accessor.HttpContext.Items.TryGetValue(nameof(Post), out var post))
{
return post as Post;
}
else
{
return new GenericPost(); // we need to return something that is either a `Post` or derivative of `Post`.
}
});
}
Here are a couple source-links for both the 2.2 and 3.0-versions if you’re interested in what happens behind the scenes:
