There is an interesting pattern that you can find in many projects, that usually starts with a good idea and turns into a dump in no time: the core folder. You start with an application and think about the core business, the important stuff. So, you go on and create a core folder. Here is now the place for the important stuff, right? No. Here is the start of your mess that from now on only grows.
There is an annoying bug in the Windows 11 Installer that catches me way too often. If you select something different than the pre-selected values in the first screen for the language options, the installer starts but then stays forever at this progress level:
42%
Many developers use GitHub to share their code. It is convenient, offers a lot of features and works without any noticeable problems for years. Did you ever thought on creating a backup for your repositories?
Git helps us to ignore that task a bit. With every git clone we create a full copy of the whole repository, what by all means is a backup. Why should we then do some extra work to get another backup? It is true that Git creates a copy. But do you have a current copy of all your repositories on GitHub somewhere easy to find? Not only the few repositories you worked on in the last month, but everything you have on GitHub up to its newest commit. Probably not.
Last week we saw how much code we can get rid of when we use the [init keyword to create immutable objects]. The only downside we found was that we cannot enforce that all properties get a value. To solve this problem, we can use the required keyword of C# 11:
The required modifier indicates that the field or property it is applied to must be initialized by an object initializer. Any expression that initializes a new instance of the type must initialize all required members. – from learn.microsoft.com
With C# 9 we got the new init keyword. You may have heard of it when it was introduced, but probably not used it much at the time. Then as with so many new things in the C# language, the new syntax did not offer new functionality but syntactic sugar to get the same results faster. Why should we care now? Because in combination with other newer features in C# that init keyword is a great help.
What was the init keyword again?
The init keyword defines an accessor method in a property or indexer. An init-only setter assigns a value to the property or the indexer element only during object construction. An init enforces immutability, so that once the object is initialized, it can't be changed. – from learn.microsoft.com
If you want to revert a change in a file with Git, you can use this command:
The double-hyphen (--) tells Git to take what follows as its second argument (the path to the file). This makes it clear that you did not specify a branch.
While this works, it is not ideal. You might wonder what command to use or where the -- should go. It can be hard to remember and we often need to check the documentation to make sure we do it the right way. Is there a better way?
Whenever we have a method that accepts a list as a parameter, we should test these 5 cases to see if the method handles the input correctly:
Let us take a closer look at each of those inputs and what they can check for us. The list is not my invention, but so far, I was unable to attribute it correctly. If you know who the source was, please let me know.
Before I start making changes, I usually run the template code to see if everything works so far. Even when it only has the template code, problems could happen. A few weeks ago, I skipped this step and after I made my changes, I got this error:
Error (active) CS0017 Program has more than one entry point defined. Compile with /main to specify the type that contains the entry point.
When we search for a library or a package, we usually have too many options. Which one should we choose? What are good approaches? The less we know about the specific topic, the less we can make a good decision.
That is where awesome lists come to play. They are curated lists by individual developers or community members that selected resources they found especially helpful. That can be packages, blog posts, tutorials, or anything else.
Last week we explored five helpful extensions for Visual Studio. In this post, we will apply the same approach to Visual Studio Code (VS Code). VS Code relies heavily on extensions to provide even the most basic language-specific support within the editor. While we are used to install language specific extensions, we should also look a bit further and try some more general extensions.