Archiv der Kategorie: .NET

Don’t return null

Erstellt am April 3, 2017 von oliverfunke

If you write a function returning an object instance you have to think about the special cases. This may be error cases or maybe situations where no object instance can be found or created. In such cases you will often … Weiterlesen →

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

Design patterns: Iterator

Erstellt am März 19, 2017 von oliverfunke

An Iterator provides a way to access the elements of an object sequentially without exposing the underlying representation. It is a base Design Patterns which we use permanently. For example a loop over a list is done by using the … Weiterlesen →

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

Design patterns: Facade

Erstellt am März 12, 2017 von oliverfunke

A Façade class provides a higher level interface to a set of sub level interfaces. This will make the subsystem easier to use. The high level interface will hide details of the low level interfaces. This may be complex workflows … Weiterlesen →

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

Use factory methods instead of overloaded constructors

Erstellt am März 5, 2017 von oliverfunke

If a class can be created and initialized in different ways or by using different kind of values you may often see overloaded constructors. This is a standard way to implement such an object creation but it has a major … Weiterlesen →

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

Linq vs Loop: Simple Query

Erstellt am Februar 26, 2017 von oliverfunke

Within this article and within further articles I want to compare Linq and classical loops. During code reviews you may sometimes hear the suggestion to use language specific features as they will simplify the source code. Such a feature is … Weiterlesen →

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

Design patterns: Factory Method vs Abstract Factory

Erstellt am Februar 19, 2017 von oliverfunke

In case a class instance shall be created, developers may give the advice to use a “factory”. This common term isn’t wrong but sometimes it’s better to define the exact type of factory you want to use. So, in this … Weiterlesen →

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

Continuous Integration

Erstellt am Januar 29, 2017 von oliverfunke

Software teams normally consist of several developers. They work independent or in small groups on their own tasks. And of course, sometimes the developed code has to be merged together to get a running application. One kind of merging principle … Weiterlesen →

Veröffentlicht unter .NET, Clean Code, Designprinzip, Projektleitung, Uncategorized | Kommentar hinterlassen

Design patterns: Factory Method

Erstellt am Januar 22, 2017 von oliverfunke

A factory method is a single method to create an object instance. The method is provided by the object itself. Therefore it can be overridden in a subclass. By using the factory method pattern the object exposes a method to … Weiterlesen →

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

Do not use Boolean function parameters

Erstellt am Januar 15, 2017 von oliverfunke

Function parameters may be of any type. So why should we try to avoid Boolean parameters? Because they have two disadvantages. The main issue is that a Boolean value may lead to a function which does several things. Furthermore the … Weiterlesen →

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

Characteristics of high quality C# code

Erstellt am Januar 8, 2017 von oliverfunke

Following you will find some characteristics for high quality C# code. Of course it is possible to define much more characteristics. So the following code quality features are an entry point to this topic only.   Define a standard constructor … Weiterlesen →

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