A few days ago, I tried to update my side-projects to .Net 4.8. With most projects this worked without any problems. But in the middle of the upgrade I got this strange error message:
Running your database with a case-insensitive collation is often a great help. If you search for 'de' you find 'de', 'De', 'dE' and 'DE' as well. However, if you need to make a case-sensitive search, that benefit is now a liability and all the other cases clutter your result.
As explained in my earlier post, Visual Studio creates a self-signed certificate for your web application that allows you to access your site over HTTPS. If you accidentally remove this certificate, your web application will fail to load and report something like ERR_CONNECTION_RESET on the default error page of your browser:
We use Selenium and Firefox to verify our BDD specifications. That combination worked well until the last update to Firefox 75. Instead of our application on the developer machine, Firefox only showed us the "Your connection is not secure error" overlay. We depend on fast feedback cycles and needed a solution quickly.
Visual Studio creates a self-signed certificate for your web application that allows you to access your site over HTTPS. As long as you do not need to change anything, this magical configuration works like a charm. Unfortunately, when you need to change something, it is incredibly hard and the magic turns into a curse.
If you want to span a row over multiple columns in an HTML table, you can use the colspan attribute on the td element. You may know the approach in which you specify the number of columns you want to span. A much simpler way to span all columns is to use 100%:
Getting parts of a string is usually a job for SUBSTRING. However, when you only care about the last two characters of a string, save yourself the troubles of calculating the starting point for the SUBSTRING function. A much simpler approach is to use the RIGHT function:
I had to check some inconsistencies in our database naming convention and needed a list of all column names inside a database. While you can find multiple solutions with Google, it took me a while until I found one that worked and was flexible enough for all my needs.
Saving the state of a container in Docker is an anti-pattern. You should create your containers in a way that you can throw them away and start with a new one. However, there are some use-cases in which a snapshot of your current container is of great help.
One such use-case is creating a snapshot of your database container for integration testing. Instead of creating a fresh database from scratch and adding the seed data before every test run, I could do that once and reuse this known good starting point. This will save a lot of time and I get the feedback of my tests faster.
Git tracks the author of every commit. If you do not modify anything, the global settings will be used. That is great for the day-to-day use, but it may not be what you want in all situations.
If you do pair-programming, you may want to make the commits as a team. If you commit your code on the command line, you can use this option with your commit:
git commit --author="John Doe <[email protected]>"