This article continues our series on multitenant ASP.NET Core applications, focusing on database connection configuration in an ASP.NET 8 application. Following our previous topics on tenant resolution and authentication, we will configure an in-memory database using Entity Framework (EF) Core. The article explores the scenario when each tenant has its own database.
In this blog post, I will describe how to calculate availability (SLA) based on logs generated for existing "Web Test" in Application Insights. We will use Azure CLI to get data from a given period and Powershell to perform simple math to get the availability percentage value.
From an accessibility point of view, it's worth considering the default font size set in the user's browser. You can easily adjust your design to this value in CSS stylesheets using relative units like rem and em. There might be a situation where you need this value from the JavaScript context. How to get it?
It's always worth being in sync with the most recent versions of libraries that you use. Naturally, it's true as long as these do not contain malicious code. In this article, you can find a simple, ready-to-use Bash script to update all NPM and NuGet packages within your .NET Core solution. Feel free to use it in your CI/CD.
How to control authentication cookie lifetime, and why is sliding expiration potentially dangerous? This article contains an overview of this topic. It also shows the way to set absolute authentication cookie lifetime in ASP.NET Core.
It's a quite frequent case that some components like input fields have many states. It may look different according to some conditions. The classic example is an incorrect value in an input field which results in a red border. How to handle this in Sass?
How to send a multipart HTTP requests containing files using HttpClient in .NET Core? What to do if the target endpoint requires some additional data? This article describes the solutions for common cases and presents raw HTTP messages that are generated by the HttpClient for multipart requests.
There are many sample solutions on the Internet that show how to use PowerBIClient in ASP.NET Core apps. The typical approach is to create a new instance of it and then use it to invoke web requests. Eventually, it is disposed. Is it a good approach?
How to create a simple infinite-scroll mechanism? This article describes how infinite scroll is implemented on this blog.
Recently I wrote a simple script for my CI/CD which was responsible for new tenant onboarding. The key thing was to add a domain to Front Door and adjust the existing routing rule. I decided to use Azure CLI for that but there were some difficulties with making routing rules handle the new domains.
In this article, we will set up multi-tenant authentication. How is it supposed to work? When a user is logged in within tenant1 then they will not be a valid user from the tenant2 point of view. We will use cookie-based authentication for that.
A multitenancy is a way to handle multiple tenants on a common infrastructure. Depending on your case, tenants may share the application itself, database, or other services. In this series, we will create ASP.NET Core multi-tenant app. This article describes a tenant resolution mechanism.
According to open-close principle, code should be open for extensions but closed for modifications. In other words, you should avoid modifying production code unless it's really necessary. A proxy design pattern is one of the solutions to this problem.
Fluent builder is a well-known design pattern that helps to build objects of a given type. It makes code more readable and maintainable thanks to method chaining. The problem occurs when you try to extend the functionality of the existing builder using inheritance.