We are in the process of deprecating many smaller subdomain app services and serving the same content through our flagship site. This pos...
Windows AzureIf you build .NET Core apps on your Mac and install https certificates to your keychain for development purposes, it’s helpful to know th...
Keychain MacOS CertificatesStandard Polyfills for Front End Getting your JavaScript applications working across all browsers is challenging. If you are writing you...
JavaScript Webpack PolyfillsStatic site hosting is straightforward, and from our experience, less likely to have errors compared to a more dynamic site. While dynami...
Azure StaticSeveral months ago, Bill Boga and I, realized there was a performance enhancement we could make in our infrastructure. We were utilizing ...
.NET PerformanceThis post covers augmenting an authenticated User for use in middleware or when using the [Authorize]-attribute in an MVC-controller. The...
ASP.NET Core IdentitySever AuthenticationIf you’re like me, you aspire to write clean and consistent scss. We use the power of scss for everything from nesting our selectors, cre...
SASSFeature flags can be useful for changing the runtime behavior of an application with minimal impact. Having a UI to toggle the feature fl...
.NET asp.net coreWhat is a machine key? According to https://docs.microsoft.com/en-us/dotnet/api/system.web.security.machinekey?view=netframework-4.7.2 a...
.NET asp.netWe’re in the process of upgrading our infrastructure to run our Azure Web Apps in multiple datacenter locations behind Azure Traffic Mana...
.NET asp.net asp.net coreIt can be tricky to run integration tests targeting a web server using the command line. Essentially, we need to: Start the applicati...
JavaScript npmI was trying to get a global .NET Core tool working on my development machine, which just so happens to be running macOS. I also work wit...
.NET macOSWe’ve moved around CSS frameworks in the past few years, Semantic UI for our application layer, and Bootstrap for our static sites. As ou...
SASSNew to the frontend at RIMdev, or looking for more about our Frontend team? Here’s a quick overview of our team, tools, and culture! As ...
Team RIMdev FrontendSimple transitions Vue.js has an extremely helpful was to handle animations in web apps. In a simple example if we want to display somet...
Vue.js JavaScript AnimationsAs web applications have gotten more complex, so has the technologies used to build them. Magic can be good when all works as intended, b...
Webpack JavascriptWe’re in the process of scaffolding out our Microsoft Azure environments using Terraform. We’re looking at deploying consistently from ma...
Azure TerraformHealth checks in ASP.NET Core are useful for reporting the health of your ASP.NET Core web application. But, this functionality can’t dir...
.NETAs I’ve walked through upgrading a number of solutions to target a new version of the .NET Framework, I’ve compiled a list of helpful ste...
.NETRead 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:
