Frameworks - Your Average Developer

Observer Design Pattern

In today’s episode of Software Design Patterns you will learn everything about the Observer Design Pattern. The Observer Pattern is pretty common and widely used. Compared to the already covered creational design patterns like Singleton and Factory Method the Observer is a behavioral pattern.

ASP.NET Core

Custom Exception Handling in .Net Core with a Middleware

For many developers, exceptions and error handling is a pain. It distracts from the application flow. However, it is important for any decent service or application to handle it well. To tackle this problem we will use Custom Exception Handling in this tutorial.

ASP.NET Core

Using OData in an ASP.NET CORE Application

At the end of this tutorial, you will be using OData v4 in an ASP.NET CORE Web Application. OData provides a powerful and stable querying language that will help you to write less code and get more.

Frameworks

C# Unit Tests with Mocks

C# Unit Tests with Mocks provide an easy way of reducing unwanted dependencies when writing unit tests. One of the best and shortest definition for mocking is “mocking is creating objects that simulate the behavior of real objects.

Angular

Property and Event Binding in Angular 2+

roperty and Event Binding in Angular 2+ is a very powerful tool offered by the Framework. You can easily pass values to child elements (Input) and emit changes (event binding) to the parent element (Output).

Frameworks

Using Dependency Injection (DI) in .NET Core

In this tutorial Using Dependency Injection (DI) in .NET Core I am going to show you how to use Dependency Injection in an .NET Core Project.

Frameworks

Dependency Inversion Principle (DIP) – S.O.L.I.D. Framework

The fifth principle within the S.O.L.I.D. Framework is the Dependency Inversion Principle. Entities must depend on abstractions not on concretions.

Frameworks

Interface Segregation Principle (ISP) – S.O.L.I.D. Framework

The 4th principle of the S.O.L.I.D. Framework is the Interface Segregation Principle - "clients should not be forced to implement interfaces they don't use.

Frameworks

Liskov's Substitution Principle (LSP) - S.O.L.I.D. Framework

The 3rd principle of the S.O.L.I.D. Framework is the Liskov's Substitution Principle - "derived types must be completely substitutable for their base types"

Frameworks

Open Closed Principle (OCP) – S.O.L.I.D. Framework

The second principle of the S.O.L.I.D. Framework is the Open Closed Principle (OCP). At the very first moment the combination of open and closed at the same time creates some confusion, but after we dig deeper it makes sense.

Frameworks

Single Responsibility Principle (SRP) - S.O.L.I.D. Framework

The S.O.L.I.D. principles are an approach to deal with software design issues. The SRP says "Every software module should have only one reason to change"