DevStory

Once, on one of my projects, we decided to upgrade from .NET Core 2.1 to the latest LTS version (3.1 at the time of writing). Prior to this, I had several experiences updating small projects, both from classic .NET and older versions of .NET Core. However, most of these projects used Dapper instead of full-fledged ORMs. I had only updated EntityFrameworkCore directly a couple of times, and it’s worth noting that I didn’t encounter any significant problems during those updates. Until this moment.

I think many who have worked with .NET Framework are familiar with the situation where you need to read the App.config configuration file, and it’s not a particularly pleasant task. You always have to create a bunch of static classes, which essentially refer to ConfigurationManager.AppSettings. Or, writing complex and unclear custom configuration sections, inserting each section into the configSection with a reference to the section’s class and its assembly, which isn’t ideal either.

Postman is a great tool for working with REST APIs, offering a wide range of features, from simple endpoint checks to writing comprehensive API tests. With it, you can mock servers based on requests or create a collection and easily share it with your team. In modern applications, token-based user authentication is frequently used, which can be somewhat inconvenient. Typically, users are provided with two tokens: access_token and refresh_token, where the access_token quickly expires and needs to be refreshed.

Many Git users, I believe, are familiar with the situation where, after making a commit, something unnecessary is found to have been included in the commit, or the committed code fails tests. Sometimes, this code even ends up being pushed directly to origin.