C # 9 is officially released with .NET 5 on November 2020. In this article, I will introduce some of the new features that I think are interesting to know.
In C# 9, you can write your main program at the top level, immediately after
using statements like the following code:
I think you guessed it, Angular is what you need to achieve this.
In this article I’m going to introduce the fundamentals of building applications with Angular. By the end of this article we will understand the basic Angular building blocks such as: Components, Modules, Templates, Data-Binding, Directives, Services and Dependency Injection.
This article is the continuation of two articles already published about learning Angular for Back-End developer. The Part 1 was a quick introduction to Angular, in which I explained step-by-step how to set up our development environment? How to create and serve our first application using Angular-CLI? How the Angular project is structured? …
This article is the continuation of the first one already published here:
In this article, I’m going to introduce the fundamentals of TypeScript in order to be comfortable with Angular framework.
This article is the continuation of the first one already published about “CQRS pattern with C# (Part 1)”, therefore, we will not go to explain CQRS proposal again. In this second part we are going to speak about MediatR Library and how it can implement read and write operations defined by CQRS.
CQRS is the acronym for Command Query Responsibility Segregation. The core idea of this pattern is to separate Read and Update operations by using different models to handle the treatment. We use commands to update data, and queries to read data.
In this article I’ll aim to clarify all parts of CQRS pattern with pretty schema and code example.
The following schema shows a traditional architecture used to query and update a database. The same model is used to write and read data.
Dependency Injection or DI is a design pattern that allows to delegate the creation of dependent objects to another entity outside the main class. DI allows programs to have loosely coupled classes. Let’s understand this with simple examples.
The following example shows a simple class
BusinessLogicLayer, it provides the necessary operations to get information from database. It creates an object of
DataAccessLayer to access to these operations.
In this above example,
BusinessLogicLayer class depends on
DataAccessLayer class. There are some problems with this approach, classes are tightly coupled :
BusinessLogicLayer class needs to create a…
In this topic, I’m trying to list different ways to connect your View and ViewModel inside your MVVM application.
As you know, the MVVM architecture is used to separate presentation and business logic of your application.
MVVM architecture consists of three parts :
- M : Refers to Model or data to be manipulated by the application
- V : Refers to View or appearance of data on the screen.
- VM : Refers to ViewModel which is responsible to allow View to interact with Model (data). …
“Xamarin.Forms” is a cross-platform toolkit that enables .NET developers to build native apps for Android, iOS and Universal Windows using C# and XAML.
XAML is used to build user interfaces and C# used to implement all behaviors and to call the application logic layer.