All .NET programmers had dealt at least once on their career with a null reference exception on a code line they wrote. Most of the times a parameter of a method is null, the code is not aware of it and the parameter is being used inside the method, for example we are accessing a property of an object. Because the value of the object is null we are getting an exception on the runtime.
Visual Studio provides a way to inform / warn us about possible null references. Let us see how we can enable this feature on our C# project.
A cool feature of C# that I lately used is the implicit operator keywords and with them we can define the way for converting one type into another one implicitly. A good scenario when you can use that is presented in this example.
Transforming a Web.config file based on the environment where an application is deployed is a common practice in .NET Framework applications to manage different settings like database connection strings, URLs, or other configuration values. In this article, we will see how to achieve this using the configuration transformation feature in Visual Studio.
This article contains a list of code lines, that use reflection to access data in classes. Reflection can be combined with Generics and even though some might think it can be hacky, I find that Reflection offers a tremendous advantage when dealing with monolithic application and you want to write reusable code, and you can not use object oriented concepts such as inheritance. Let’s start without further delay.