Archiv der Kategorie: C#

Design patterns: Command

Erstellt am November 26, 2017 von oliverfunke

The Command design pattern encapsulates a request as an object. This will allow adding additional functionality to the request. A typical example is the undo/redo functionality. The command object will be used as mediator between the client and the receiver … Weiterlesen →

Veröffentlicht unter .NET, C#, Design Pattern | Kommentar hinterlassen

Methods should do one thing only

Erstellt am November 5, 2017 von oliverfunke

According to the Single Responsibility Principle a class should have one, and only one, reason to change. To same statement is valid for methods. A method should do one thing only and therefore have only one reason to change. Unfortunately … Weiterlesen →

Veröffentlicht unter .NET, C#, Clean Code | Kommentar hinterlassen

Dependency Inversion by using the Unity Injection Constructor

Erstellt am August 27, 2017 von oliverfunke

One of the five SOLID principles is Dependency Inversion. To implement according to this principle you can use interfaces and dependency injection. As a software application normally consists of hundreds or thousands of objects you will have to set up … Weiterlesen →

Veröffentlicht unter .NET, C#, Design Pattern | Kommentar hinterlassen

Linq vs Loop: Join

Erstellt am Juli 23, 2017 von oliverfunke

Like in the previous article of this series I want to compare Linq with a classical loop. This time we want to look at data objects which shall be joined to create a result. Again we want to use validated … Weiterlesen →

Veröffentlicht unter .NET, C#, LINQ | Kommentar hinterlassen

Linq vs Loop: Nested Loop

Erstellt am Juli 9, 2017 von oliverfunke

Like in the previous article of this series I want to compare Linq with a classical loop. This time we want to look at the use case to handle data which contains nested data. Again we want to use validated … Weiterlesen →

Veröffentlicht unter .NET, C#, Clean Code, LINQ | Kommentar hinterlassen

Design patterns: Composite

Erstellt am Juli 2, 2017 von oliverfunke

The composite design pattern is used to compose objects into a tree structure. So each element can hold a list of sub elements. Optional it may have a link to the parent object within the tree. Within the following example … Weiterlesen →

Veröffentlicht unter .NET, C#, Design Pattern | Kommentar hinterlassen

Crash course: Asynchronous Programming with async and await

Erstellt am Juni 11, 2017 von oliverfunke

With the .NET Framework 4.5 the new keywords “async” and “await” were introduced. These keywords will aloe an asynchronous programming which is nearly as easy as synchronous programming. With this article I want to give you a crash course into … Weiterlesen →

Veröffentlicht unter .NET, C#, Crashkurs | Kommentar hinterlassen

Design patterns: Singleton

Erstellt am Mai 21, 2017 von oliverfunke

By using the Singleton design pattern you ensure that a class has only one instance. The instance operation is provided by the class itself. So it maintains its own unique instance. The .NET framework offers a very simple and thread-safe … Weiterlesen →

Veröffentlicht unter .NET, C#, Design Pattern | Kommentar hinterlassen

Design patterns: Proxy

Erstellt am Mai 7, 2017 von oliverfunke

The idea of the Proxy design pattern is to provide a substitute for another object were the substitute controls the access to the other project. So there is one real subject with a given interface, for example an object to … Weiterlesen →

Veröffentlicht unter .NET, C#, Design Pattern | Kommentar hinterlassen

Write clean code instead of comments

Erstellt am April 30, 2017 von oliverfunke

Of course comments help to understand code. They are an essential part of the source code. But comments are an addition only. If you want to create readable and easy to understand source code, you have to focus on the … Weiterlesen →

Veröffentlicht unter .NET, C#, Clean Code | Kommentar hinterlassen