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.
A few months ago, my co-worker Lukas run into a problem when he wanted to deploy code with pipelines in Azure DevOps. As a final step, he needed to restart the web server. That is no problem in an interactive session on the machine itself, you just add sudo in front of the command and enter your password. Doing this as part of a pipeline is not a great idea – you would need to write down your password and put it into Azure DevOps.
Sometimes your Git repositories move to another location. You certainly can throw your local copy away and clone it from the new location. However, there is a simpler way that only requires you to update the remote URL and you can continue with your local copy – including all your unpushed changes.
Like all web servers, Microsoft’s Internet Information Server (IIS) sends its version number with every response:
All of a sudden, our build agent could no longer communicate with Azure. A failed network change forced us to set a proxy server manually. While most browsers use the system proxy, the build agent did not.
It is the time of the year where most new year's resolutions are already forgotten. Should you still want to learn new things I have a great podcast for your. It is not about the shiny new frameworks, instead it will help you to improve your existing applications.
The podcast Legacy Code Rocks! hosted by Andrea Goulet and M. Scott Ford is my favourite one. They know what they are talking about and find guests that have interesting insights to share. I am constantly surprised how much I can learn from every episode and how much of those things can be applied 1:1 to my applications – and that by just spending between 30 and 45 minutes per episode.