Development With A Dot
Blog on development in general, and specifically on .NET. Created and maintained by Ricardo Peres.
-
ASP.NET Core Pitfalls – Dependency Injection Lifetime Validation
As you can imagine, it doesn’t make much sense to have a service that is registered as singleton to depend on another service that is registered as scoped, because the singleton instantiation will only happen once. Take this example:
-
ASP.NET Core Pitfalls Index
Last update on March 25th. Reversed order, latest ones first.
-
ASP.NET Core Pitfalls – Returning a Custom Service Provider from ConfigureServices
In pre-3.1 versions of ASP.NET Core, you could return your own service provider (AutoFac, Ninject, etc) by returning some IServiceProvider-implementing class from the ConfigureServices method. This is no longer supporting, and having code like this results in an NotSupportedException being thrown at startup:
-
ASP.NET Core Pitfalls - Localization with Shared Resources
When localizing a web application using resources, there are two common ways:
-
ASP.NET Core Pitfalls – Areas
There are a few problems with using areas:
-
Modern Web Development with ASP.NET Core 3 Discount Code
-
SharedFlat and Databases
This post is part of a series on SharedFlat. See here the first (introduction) and here the second (UI). This time I will be explaining how SharedFlat handles multitenant databases.
-
SharedFlat and Multitenant UI
In my previous post, I introduced SharedFlat, a library for making multitenant ASP.NET Core apps easier to build. This time I’m going to talk about how can we customize the UI per tenant.
-
Introducing SharedFlat
A multitenant web application is one that responds differently depending on how it is addressed (the tenant). This kind of architecture has become very popular, because a single code base and deployment can serve many different tenants.
-
Modern Web Development with ASP.NET Core 3 - Second Edition
