Attention: We are retiring the ASP.NET Community Blogs. Learn more >

Contents tagged with Dotnet Core

  • Sorting and Paging in Blazor using EF Core

    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.

  • Get Started with Azure Functions

    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.

  • Token Based Authentication in Dotnet Core 3.0

    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.

  • CRUD using Blazor and Entity Framework Core

    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.

  • Versioning Web API

    Change is an inevitable factor in the life cycle of an API.  More and more organizations today face a dynamic and changing environment.  The change is driven by factors within the enterprise like implement a new business model, expand to a new market. It can also be external such as disruptive technologies, new government regulations, changes happen in partner/consumer organization, etc. I will talk about versioning in general and versioning Web API using multiple versioning strategies in detail in this post.