.NET 6, A guide for the high impact Breaking Changes
.NET 6 is the first Long-Term-Support (LTS) version since the “one .NET to rule them all” era, which means it’s plan as future-proof. It includes a tone of improvements and changes that are planned to live long, thing that brought with it a few high impact Breaking Changes. Although there are lower impact braking changes too, this guide will help you identify if any of the important ones really affect you, and provide a suggestion at the same time.
Create and use your first component in Blazor!
Blazor, the new client-side UI framework from the ASP.NET team, is definitely making a splash among the developers that were trying to avoid the JavaScript coding experience (or even better the debugging JavaScript experience!).
Migrating to .NET 5 – A few clicks away!
Before you actually start reading this article, I have to be honest with you: Unless your app is a Blazor app, you don’t need to read this; all you need is to download .NET 5, change the target framework in your project properties and that’s it…! Then again, if you need the download links or want to check the process I followed, feel free!
Things you should know about .NET 5
I know many of you are waiting for an LTS to jump in and upgrade your systems, but I think this time things are a bit different! First of all, the next LTS will be .NET 6 which is planned for November 2021, and secondly .NET 5 is already published two months ago as RC1. Actually, two release candidates of .NET 5 were published and tested by many before the actual release:
Early vs Late Binding, reflection, and type dynamic in C#
Most script languages use late binding and most compiled languages use early binding; C#, although a compiled language and thus an early binding one, has reflection for late binding. In this post we will explore early & late binding in C# with theory and samples.
An error occurred while starting the application, Process Failure and many more
It comes in many colors and flavors, it is usually a headache because there are multiple reasons why you can get this, it usually includes no (or minimal) information in Application log, and if you are unlucky enough to have two problems that cause this, it is a guaranteed bad day.