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]>"
One working project failed to compile after I made a fresh checkout. The same commit that before worked without a problem now got me this compiler error:
Could not find a part of the path C:\*****\bin\roslyn\csc.exe
When we tried our first attempt to disable unsecure protocols, we run into an annoying problem on the servers that run SQL Server. After disabling all the outdated security protocols, we could no longer connect to our databases. The error message was no help at all:
The internet moves on and the next big thing that gets dropped is the support for older versions of TLS (Transport Layer Security). If you not already have done so, now would be a good time to check that your server understands TLS 1.2 and disable the older versions of TLS on your web servers.
On the 3th of March 2020 .Net Core 3.0 reaches the end of support. It is not a long term supported version and if you did not upgrade to 3.1 yet, you definitely should wait no longer. We did the upgrade for the .Net User Group Bern site two months ago and had no problems at all. Upgrading from 2.2. to 3.0 was a big challenge where Daniel and René had to do a lot of work.
An often-overlooked combination of tools to develop software are pen and paper. Don't panic, I do not propose to write a first draft of your code on paper and only use a computer for the final version. Some universities or companies in their hiring process may do that, but that is not what I mean.
Last week I did something stupid: While working in the train I decided now would be a good time to upgrade ReSharper to the newest version. It took far longer than expected and when the train reached my station, I had to put my laptop into the sleep mode. As I started it again in the next morning, the ReSharper installation finished and everything looked fine. Except it was not.
When you let SQL Server create the primary keys for a table and try to insert a specific key, you will get this error message:
Cannot insert explicit value for identity column in table 'MyTable' when IDENTITY_INSERT is set to OFF.