Archiv der Kategorie: .NET

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

Clean Tuples

Erstellt am Mai 28, 2017 von oliverfunke

Depending on the preferences of a developer you may sometimes find a lot of tuples within the source code. Whether this is good or bad practice is another discussion which is not part of this article. Therefore I don’t want … Weiterlesen →

Veröffentlicht unter .NET, C++, Clean Code | 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

Design patterns: Observer

Erstellt am April 23, 2017 von oliverfunke

The Observer design pattern is used when you want to define a one-to-many dependency between objects. In case one object changes its state, all its dependents are notified and updated automatically. In this design pattern you have two participants. The … Weiterlesen →

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

Linq vs Loop: Check whether item exists

Erstellt am April 16, 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 common use case to check whether an item exists. Again we want to use validated … Weiterlesen →

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

Design patterns: Adapter

Erstellt am April 9, 2017 von oliverfunke

The Adapter design pattern, which is also known as Wrapper design pattern, is used to convert the interface of an existing class into an interface expected by the client. In such a case the existing class has an incompatible interface. … Weiterlesen →

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