Blog of Pi

In the last decade, I was part of some consulting assignments with our customers for Cloud Adoption.  Quick and easy setup, no maintenance, no long-term contracts, High flexibility, and Maximum uptime are some of the key benefits we used to influence business to move to Cloud.  While I advocate for Cloud adoption and cost savings because of it, one of our new customers who already migrated to Azure came to us with a different requirement.  They want to maximize cost savings in Azure. 

In my last post (CRUD using Blazor and Entity Framework Core), we discussed implementing CRUD using Entity Framework Core.  We also talked about Templated Components, Communication between components, etc.  In this post, we will see about implementing Sorting and Paging in Blazor using EF Core and Web API.  You will be familiar with the following topics after this post.

Serverless architecture also called as Function-as-a-Service is an event-triggered computing model.  “Serverless” doesn’t mean there are no servers.  They are abstracted so the developers are free from having to manage servers and enable them to focus on writing code.  Serverless code is event-driven and the trigger can be anything from an HTTP request to a Blob.  I will talk about Microsoft Azure’s serverless offering Azure Functions in this post.  Let’s get started with Azure Functions.

APIs are now the standard for building and integrating modern applications.  It also evolved as the key enabler in conducting risk-free legacy modernization and they become engines of innovation.  In addition, exposing the services via APIs allows organizations to reach a larger audience, expand into new areas, and reuse existing assets.  Providing security to these APIs is one of the main concerns.  In this post, we will talk about using Token Based Authentication in Dotnet Core.

In my last post (CRUD using Blazor and Entity Framework Core), we discussed using Entity Framework Core with Blazor and implement CRUD functionalities.  We also discussed the usage of Bootstrap, Validations using Data Annotations and Creation of Dynamic content using RenderFragment. In this post, we will see how to implement a cascading dropdown in Blazor.

In my last post (Get Started with Blazor), we discussed the Blazor Framework, Hosting models and how to set up authentication and authorization in a Blazor server-side application with an example.  In this post, I am going to explain CRUD using Blazor and Entity Framework Core.  I will use the sample application we have created in the previous post and extend it with the new functionalities we are going to talk about in this post.  You will be familiar with the following topics after you read this post.

Blazor is a new web UI framework based on C#, Razor, and HTML.  This runs in the browser via WebAssembly.  It helps build interactive web UI using C# instead of JavaScript.  This post demonstrates how to build a SPA using Blazor.  Blazor simplifies the task of building fast and beautiful SPAs that run in any browser. It does this by enabling developers to write Dotnet based web apps that run client-side in web browsers using open web standards. Let’s get started with Blazor.

In my previous article, I explained about restricting users based on the IP Address.  It was implemented by using a whitelist of IP Address and middleware.  The solution helps authorize users on application level.  I also mentioned that, I will write another article to explain about restricting users on a controller level or action level.  Policy based authorization is a new feature introduced in Dotnet Core that allows you to implement the application authorization rules in code.  In this post, I will explain about Policy based authorization in ASP.NET Core with an implementation example.