Two of the key concepts in object-oriented programming (OOP) are inheritance and composition. While both can help you reuse code, there are key differences between them. Inheritance establishes common behavior and interfaces for your classes, while composition combines and reuses existing classes to create more complex objects.

In this article, we’ll dive into these two concepts of OOP and understand when, why, and how to use them in our .NET applications. To work with the code examples provided in this article, you should have Visual Studio 2022 installed in your system. If you don’t already have a copy, you can download Visual Studio 2022 here.

To read this article in full, please click here

The Dapper ORM (object-relational mapper) has gained widespread popularity for working with databases in .NET because of its high speed and simplicity. We learned the basics of working with Dapper in a previous article here. We also discussed working with the Dapper Extensions library in an earlier article. In this article, we’ll take a look at some advanced features of Dapper.

To use the code examples provided in this article, you should have Visual Studio 2022 installed in your system. If you don’t already have a copy, you can download Visual Studio 2022 here.

To read this article in full, please click here

When building an ASP.NET Core application, you can draw on various middleware components to inspect, route, or modify the request and response messages that flow through the pipeline. You can also write your own custom middleware in ASP.NET Core.

Usually, you have a chain of middleware components in the application pipeline in ASP.NET Core. In this article, we’ll examine middleware in ASP.NET Core and how we can work with the convention-based and factory-based approaches.

To use the code examples provided in this article, you should have Visual Studio 2022 installed in your system. If you don’t already have a copy, you can download Visual Studio 2022 here.

To read this article in full, please click here

Rate limiting is a technique used to restrict the number of requests allowed to a particular resource in a specific time window to thwart DDoS attacks and API abuses. When a rate limiting threshold is reached, subsequent requests to the resource are disallowed, delayed, or throttled.

In a previous article, I discussed how to get started with the new rate limiting middleware in ASP.NET Core 7. In this article, I’ll examine the four different rate limiter algorithms available in ASP.NET Core 7: fixed window, sliding window, token bucket, and concurrency. 

To read this article in full, please click here

As a thoroughly modern web framework, ASP.NET Core has built-in support for response compression, allowing you to reduce the size of responses and shorten response times. In this article we will examine how response compression works and how we can take advantage of response compression middleware in ASP.NET Core.

Compression is an easy way to reduce network traffic and increase the speed of communication between web server resources and clients or consumers. The popular algorithms available to achieve this compression include Brotli, Gzip, and Deflate, and most modern-day web browsers support response compression. ASP.NET Core’s response compression middleware uses Brotli or Gzip compression by default, depending on which is supported by the client. 

To read this article in full, please click here

Minimal APIs in ASP.NET Core allow you to easily create RESTful APIs with minimal code and configuration. No matter what type of API we build, it is always important to minimize the amount of data transferred over the network, which saves bandwidth and improves the responsiveness of the app. We do this by compressing the payloads of both requests and responses. 

Of course, that means we must decompress those payloads at the other end. In ASP.NET Core 7, request decompression is supported out of the box: You can now use the new request decompression middleware to enable your API endpoints to accept requests that have compressed data.

This article examines how you can work with request compression and decompression in ASP.NET Core 7 Minimal APIs. (Note that we discussed response compression in ASP.NET Core in a previous article.) To use the code examples provided in this article, you should have Visual Studio 2022 installed in your system. If you don’t already have a copy, you can download Visual Studio 2022 here.

To read this article in full, please click here

The never-ending quest to enhance the quality of our code and improve its readability, maintainability, and performance has produced a number of architectural and design principles over the years. The DRY (“Don’t repeat yourself”), YAGNI (“You’re not gonna need it”), and KISS (“Keep it simple, stupid”) principles are three we should all keep in mind when we code.

These three acronyms represent concepts that can help streamline your development process as well as make your code simpler, cleaner, and more maintainable. We will examine these three principles here as well as learn how they can be applied to the code of your .NET applications.

To work with the code examples provided in this article, you should have Visual Studio 2022 installed in your system. If you don’t already have a copy, you can download Visual Studio 2022 here.

To read this article in full, please click here

In most any business application, you will store and retrieve data from a data store by performing CRUD operations (create, read, update, and delete). In this regard, there are several technologies and tools you can use. For example, you can choose from the available ORM frameworks such as Entity Framework, Dapper, or NHibernate.

However, the challenges go beyond storing and retrieving data. You want to use a tool or an approach that helps you write reusable, maintainable, and flexible code. For that, you can draw on design patterns such as the repository and unit of work patterns.

We examined the repository design pattern in an earlier article here. In this article, we’ll explore the unit of work design pattern with relevant code examples to illustrate the concepts covered.

To read this article in full, please click here

Rate limiting is a technique used to restrict the number of requests allowed to a particular resource to thwart DDoS attacks and API abuses. Once a rate limiting threshold is reached, subsequent requests to the resource are disallowed, delayed, or throttled.

Until .NET 7, implementing rate limiting in ASP.NET Core applications required using third-party packages such as AspNetCoreRateLimit. But with ASP.NET Core 7, rate limiting is now a built-in feature, available as a middleware designed to prevent abuse, protect against attacks, and ensure fair resource allocation.

I discussed how to use AspNetCoreRateLimit to implement rate limiting in earlier versions of ASP.NET Core in a previous article. In this article, we’ll examine how to use the new built-in rate limiting middleware in ASP.NET Core 7.

To read this article in full, please click here

An object-database mapper for .NET Core, Entity Framework Core is the open-source, cross-platform counterpart of the Entity Framework ORM (object-relational mapper) for .NET. Among the notable features of EF Core is the ability to carry out migrations to update your database schemas and ensure they are kept in sync with the data models of your applications.

In this article, we will delve into the rudiments of using EF Core migrations in ASP.NET Core 7 applications. To use the code examples provided in this article, you should have Visual Studio 2022 installed in your system. If you don’t already have a copy, you can download Visual Studio 2022 here.

To read this article in full, please click here

In ASP.NET Core 7, minimal APIs provide a lightweight way to create web APIs with less boilerplate code. However, errors can still occur and you should be able to handle them elegantly.

This article discusses how we can handle errors gracefully in minimal API apps in ASP.NET Core 7. To use the code examples provided in this article, you should have Visual Studio 2022 installed in your system. If you don’t already have a copy, you can download Visual Studio 2022 here.

Create an ASP.NET Core 7 minimal Web API project in Visual Studio 2022

First off, let’s create an ASP.NET Core 7 project in Visual Studio 2022. Follow these steps:

To read this article in full, please click here

You will often have the need to send emails through your application. There are several tools and libraries available to help you achieve this. And cloud-based email services with friendly APIs make it easy to incorporate rich email services into your applications. One of the most popular and useful cloud-based email services is SendGrid.

SendGrid can help businesses and developers send both marketing and transactional emails. It provides a simple, reliable, and scalable email infrastructure that allows companies to focus on their core operations while ensuring their emails are delivered to the intended recipients. And SendGrid provides an API and libraries for many different programming languages and frameworks including C# and .NET. 

To read this article in full, please click here

Minimal APIs are a type of API in ASP.NET Core that includes a bare minimum of files, features, and dependencies. Minimal APIs allow you to build fully functional REST endpoints with minimal coding and configuration. One of many new enhancements in ASP.NET Core 7 is its support for parameter binding in minimal APIs.

The goal of this post is to give you a head start on working with parameter binding in minimal APIs. To use the code examples provided in this article, you should have Visual Studio 2022 installed in your system. If you don’t already have a copy, you can download Visual Studio 2022 here.

To read this article in full, please click here

As more businesses adopt microservice architectures for their applications, more developers have had to grapple with the concepts of orchestration and choreography. Although these terms are sometimes used interchangeably, there are key differences between these two architectural patterns.

Orchestration is a centralized approach to making all control decisions about interactions between services. Here a central orchestrator service coordinates all of the other services that execute a business transaction or workflow. By contrast, a choreography is a decentralized approach to coordinating this workflow, where each service determines its own behavior based on the messages it receives from other services.

To read this article in full, please click here

A major part of Microsoft’s “cloud-first” .NET 7 release in November, ASP.NET Core 7 brings powerful new tools to the web development framework to help developers create modern web applications. Built on top of the .NET Core runtime, ASP.NET Core 7 has everything you need to build cutting-edge web user interfaces and robust back-end services on Windows, Linux, and macOS alike.

This article discusses the biggest highlights in ASP.NET Core 7, and includes some code examples to get you started with the new features. To work with the code examples provided in this article, you should have Visual Studio 2022 installed in your computer. If you don’t have a copy, you can download Visual Studio 2022 here.

To read this article in full, please click here