Goodbye 2024, Welcome 2025
With only a few hours remaining of 2024, it is time to look back and take a tiny outlook on 2025.
With only a few hours remaining of 2024, it is time to look back and take a tiny outlook on 2025.
A rather annoying error caught my attention a few weeks ago. Our SonarQube pipeline in Azure DevOps started to throw this error:
A few weeks ago, I upgraded my Synology DiskStation to the newest version of the DSM 7.2 branch. The upgrade warned about a few incompatibilities, but I used none of them – at least I thought. While the upgrade went through without any problems, it took a while to notice an odd new problem. When I tried to log in via SSH, all I got was the access denied message.
Strange, then the Passwordless Backup with Synology DiskStation worked as it did before, yet I could not connect with the same credentials.
With the utter disaster of the NuGet auditing out of the picture and a fix for the missing CSS files in place, I finally could work with Visual Studio and see which features I found interesting in the release note do indeed add some value in my daily work.
A few weeks ago, I noticed a nice feature of GitHub: we can create links to code on GitHub and highlight the lines we talk about. I find this a great help and show you in this post how to do it.
Last week we addressed the most annoying problem of Visual Studio 17.12, the messed up NuGet audit for vulnerabilities. This gives us now the chance to talk about the second big problem we may run into in Visual Studio 17.12: the missing CSS and JS files when we build our web applications.
Together with .Net 9 we got a new Visual Studio version. Not a Visual Studio 2025 or something that signals the significance of the version change. No, we got the small step of 17.11 to 17.12 and may give not much notice to all the changes – and they are big.
By default, dotnet runs the newest version that it finds on our machine. While most of the time that is not a problem, it looks a bit different when a new version of .Net is out. Then we may not yet be ready to upgrade and wish to use the older .Net version. But how can we do that?
As with many other websites these days, the number of page views for this blog has plummeted. The lower the numbers are, the more important it would be for the statistics tool to report the correct numbers. Unfortunately, Jetpack Stats is not up to the task. After collecting data for the last 12 months, I concluded that Jetpack misses up to 30% of the page views.
While adding a new step to our data synchronisation, I run into this error message from SQL Server Integration Services (SSIS):
Column "MyColumn" cannot convert between Unicode and non-Unicode string data types.