Last week we focused on reading RSS and Atom feeds, while this post is all about publishing our own feed. Before you can jump into writing code, you should read up on the different versions of RSS and Atom – especially when you want to use the plain XML approach.
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.
We decommissioned an older application and for the clean-up phase we had to delete the Windows Services for this application. Uninstalling the services took longer than expected, even if it should be a straightforward action.
While installing SQL Server on a new SSD, I run into a problem with the installer. Everything worked, except the add-on features I selected failed. Strange. But then SQL Server did not start, and I found this entry in the Event Viewer:
A quick hack to get a first shippable product out the door can survive a lot longer than you think. My little story shows you how things can end up if you do the right thing by pure chance.
After spending the last four months diving into performance testing and hunting down memory leaks, this series comes to an end. Let’s take a moment to reflect on the key insights and explore some ideas you can try on your own.
When we talk about performance tests, we usually do it with the goal of making our applications faster. However, we can also focus on the reduction of resources we need to deliver the same performance. If we do not want to blindly meddle with our infrastructure, we need to run our performance tests to guide the optimisation. Let us explore our options.
Last year we moved our applications from .Net 6 to .Net 8. It was much less work that it was to move from .Net 4.8 to .Net 6. The migration itself was straightforward, and we could put our updated application into production without any issues. That was until a week later when we got this strange error:
Application '/LM/W3SVC/11/ROOT' with physical root '...'
hit unexpected managed exception, exception code = '0xe0434352'.
First 30KB characters of captured stdout and stderr logs:
Out of memory.