We run into a strange error last week when we no longer could install NuGet packages from our Azure DevOps feed. Visual Studio only gave us a basic error message about SSL connections, but to get some details we needed to run dotnet restore:
error : The SSL connection could not be established, see inner exception. error : Authentication failed because the remote party sent a TLS alert: 'HandshakeFailure'.
While solving the annoying problem with the *.bacpac files, I was not sure what edition of SQL Server I have installed on my machine. The simplest way to figure out what edition you run is to start SQL Server Management Studio, connect to your SQL Server and right click on the Server node. In the Properties you find an entry for the Product and that shows what edition you use:
With a higher usage of our build agents in Azure DevOps, we run out of disk space twice in the same week. It was now time to find a solution that would declutter our local build agents.
The last time I searched for a solution I could not find anything that would allow me to clean up the working directory of a build agent without creating a solution by myself. Luckily, Microsoft listened to the countless complaints and created a solution directly in the build agent pool of Azure DevOps.
SQL Server Management Studio may not include all important parts of your table when you let it write the CREATE TABLE script. For instance, the full-text index for a table is omitted by default. If you use the full-text search feature, you should make sure that SQL Server Management Studio includes them in the create scripts. You can change the behaviour with these steps:
If you cannot restore your NuGet files because of a missing entry for NuGet.org or any other problem, open the root folder of your project and run this command:
A while ago we noticed a performance problem with Seq and the other applications that run on the same server. As it turned out, Seq allocated all the memory and left next to nothing for the other applications. A restart of Seq will only be a temporary solution, for a more durable one we need to restrict the memory consumption of Seq. Luckily, we can do that with a simple change in the configuration.
We use AsciiDoc as the format for our documentation for the user group project. AsciiDoc is a bit like Markdown, but it supports multi-file documents out of the box and without any quirks.
We use the Ruby app Asciidoctor to turn our AsciiDoc files into a PDF as part of our build job. Since building the whole application takes time, it is not the fastest way to get feedback when we write the documentation. To shorten the feedback cycle, we put Asciidoctor into a development container to create the PDF whenever we want to check something.
I was a happy user of the Moq library for the last 12 years. I liked the simplicity of Moq and how it allowed me to write tests first and then incrementally build the functionality.
Unfortunately, the creator of Moq is currently doing his best to kill the project. As he declared, either his spyware SponsorLink strong-arms enough individual developers into sponsoring him, or he will quit developing Moq. This leaves us in a lose-lose situation and for me it is time to move my private projects to another mocking library.
I played with a few alternatives and finally settled with NSubstitute. It covers all my use cases and offers an even simpler syntax than what I know from Moq.
My Ubuntu machine nagged me with notifications like this one:
Pending update of chromium snap: Close the app to avoid disruption (5 days left)
On this day 10 years ago, I was putting the finishing touches on the first blog posts I was going to publish on this blog. What started with a 12 posts series on RavenDB continued for much longer than I had anticipated. Including this post, I published 580 posts on various topics covering .Net, Python, SQL, and Testing: