Writing Multitenant ASP.NET Core Applications

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. In this post, I will present some of the concepts and challenges behind multitenant ASP.NET Core apps. Let’s consider what it takes to write a multitenant ASP.NET Core app. For the sake of simplicity, let’s consider two imaginary tenants, ABC and XYZ. We won’t go into all that is involved in writing a multitenant app, but we will get a glimpse of all the relevant stuff that is involved in it.
What Is a Tenant?
A tenant has a specific identity, and an application that responds to a particular tenant behaves differently from another tenant. Specifically, one or more of these may change:

Link: https://dzone.com/articles/writing-multitenant-aspnet-core-applications?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

Blazor Application Bootstrap and Lifecycle Methods

We have seen in my last article how web assembly and C# can be a game changer and will help the C# to run on Browser so moving to the next article, let’s see how we can setup Blazor in our machine and how we can get started with our first application with Blazor.

Environment setup.
Application Bootstrap Process.
Application Life Cycle Methods.

1. Environment Setup
While writing this article, the new experimental Blazor framework 0.0.4 was announced by Microsoft. To get this version there are few prerequisites, defined below:

Link: https://dzone.com/articles/blazor-application-bootstrap-and-life-cycle-method?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

Configuring HTTPS in ASP.NET Core 2.1

Finally, HTTPS gets into ASP.NET Core. It was there before back in 1.1, but was kinda tricky to configure. It was available in 2.0 bit not configured by default. Now it is part of the default configuration and pretty much visible and present to the developers who will create a new ASP.NET Core 2.1 project.
So the title of this blog post is pretty much misleading because you don’t need to configure HTTPS, because it already is configured. So let’s have a look how it is configured and how it can be customized. First, create a new ASP.NET Core 2.1 web application.

Link: https://dzone.com/articles/configuring-https-in-aspnet-core-21?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

Injecting Services to ASP.NET Core Controller Actions

ASP.NET Core comes with a thin but rich and powerful built-in dependency injection mechanism we can use to inject instances to controllers and some other parts of web applications. Although constructor injection is the most famous dependency injection method for controllers, there is also dependency injection to controller actions available. This post introduces controller action injection and shows how to benefit from it.
Constructor Injection With Controllers
Controller action injection is a great feature to use with controllers where most of the actions need some specific service that others don’t need. In ASP.NET Core, it’s traditional to use constructor injection. Let’s take a look at the following controller.

Link: https://dzone.com/articles/injecting-services-to-aspnet-core-controller-actio?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

Book Review: ASP.NET Core 2 and Angular 5

Last fall, I did my first technical review of a book written by Valerio De Sanctis, called ASP.NET Core 2 and Angular 5. This book is about how to use Visual Studio 2017 to create a Single Page Application using ASP.NET Core and Angular.
About This Book
The full title is ” ASP.NET Core 2 and Angular 5: Full-Stack Web Development with .NET Core and Angular" and was published by PacktPub and also available on Amazon. It is available as a printed version and via various e-book formats.

Link: https://dzone.com/articles/book-review-aspnet-core-2-and-angular-5?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

ASP.NET Core Identity Scaffolding

ASP.NET Core 2.1 introduces Razor UI class libraries that allow us to share UI artifacts with libraries and NuGet packages. One of the first official packages delivered with UI pieces is ASP.NET Core Identity. This blog post shows how to override default views of ASP.NET Core Identity by using scaffolding.
Let’s start with ASP.NET Core 2.1 application that uses individual accounts for users.

Link: https://dzone.com/articles/aspnet-core-identity-scaffolding?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

What Are Web Developers Favorite Back-End Tools? Packt’s Report Reveals All

If you’re a backend developer, it’s easy to feel overwhelmed by the range of backend development tools available. It goes without saying that you should use what works for you but sometimes it’s not that easy to even work that out.
With this in mind, this year’s Skill Up report offers a useful insight into some of the most popular backend tools being used today. Let’s take a look at what tools came out on top. That should help you make decisions about what you’re going to use or maybe even just learn.

Link: https://dzone.com/articles/the-best-backend-tools-in-web-development?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

Running an ASP.NET Core Application as a Windows Service

ASP.NET Core 2.1 introduces a new application host for Windows services. We can now run ASP.NET Core applications as Windows services with minimal effort. This blog post introduces how it is done and how to build and run Windows services on ASP.NET Core without any need for dirty hacks.
Creating a Default Web Application
We start with new default ASP.NET Core 2.1 web application.

Link: https://dzone.com/articles/running-aspnet-core-application-as-windows-service?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev