Since there is no more a single social network where we can find all the interesting things that happen in software development, it may be time to go back to the old technologies and revive RSS and Atom feeds. That way at least we can collect the many different blogs into a single source and build up on that.
This year the NDC Oslo conference was a bit earlier than usual and so I went in May to Oslo. That gave me the opportunity to attend the 17th of May parade and experience an overcrowded city centre – quiet a difference to the usual state of the city.
The conference was once more impressive and well organized. It was great to hear that with 2500 attendees this year’s NDC Oslo was back near the record heights.
I started the conference week with a workshop on Designing APIs. While it was good, it did not match the quality of last year's workshop on High Performance .NET Development.
With a year delay I could attend the workshop on Designing APIs by Irina Dominte (Scurtu). As we will soon be starting a major new API project, the timing of the workshop could not have been better.
A rather annoying error caught my attention a few weeks ago. Our SonarQube pipeline in Azure DevOps started to throw this error:
After updating the SonarQube tasks in our Azure DevOps pipeline, we got this error message:
java.lang.UnsupportedClassVersionError: org/sonarsource/scanner/cli/Main has been compiled by a more recent version of the Java Runtime (class file version 61.0), this version of the Java Runtime only recognizes class file versions up to 57.0
When we run our ASP.NET application from the command line, we see that it only starts the HTTP port:
info: Microsoft.Hosting.Lifetime[14] Now listening on: https://localhost:5155 info: Microsoft.Hosting.Lifetime[0] Application started. Press Ctrl+C to shut down. info: Microsoft.Hosting.Lifetime[0] Hosting environment: Development info: Microsoft.Hosting.Lifetime[0] Content root path: C:\Users\jg\source\repos\WebApplication1\WebApplication1
For the last few weeks, I got this annoying behaviour in the Windows task manager: When I started it and went to the performance tab, it showed the current system load and then it stops. The screen freezes and the values are no longer updated.
When it comes to testing, we usually hear that the tests are too slow. While that is a problem, we can also run into unexpected problems if the tests run too fast.
We had this line in one of our tests that checks with Fluent Assertions that the newest entry for our order history was written in the last minute:
Hangfire is a great tool to for background processing in .Net. We use it for all our projects, and it works without any problems.
There is only one bit of nitpicking we found: If you use Hangfire with multiple projects, it is a bit hard to keep the dashboards apart. By default, the tile reads "Hangfire Dashboard" in all of them:
When we start a new project, we best create a Git repository right away. The only problem when we do that from the command line is that we do not get a .gitignore file. Without such a file, Git will track all files in our repository – including *.exe, *.dll, *.pdp and many more that we do not want. We could go and find a .gitignore from a different project. But there is a better way for our .Net projects: