SQL Server offers an integrated alarming system that informs you by email when something goes wrong. In the past this helped us find problems early on and react quickly – before we lost data. Let us look how we can activate this feature in SQL Server.
After the installation and the enforced reboot of my machine, Docker Desktop for Windows did not bother to start. I got the Docker command line application in the Command Prompt, but the hello-world example ended with an error:
One problem that annoyed me for months was the missing code coverage in our build jobs in Azure DevOps. The metric vanished from one day to another for the .Net 4.x projects. Whatever I tried with the options in the Visual Studio Test task, all I could produce was this link to the Microsoft documentation:
After updating some NuGet packages, one of our .net 4.7.2 projects throw this error when we try to build it:
Error: Your project does not reference ".NETFramework,Version=v4.7.2" framework. Add a reference to ".NETFramework,Version=v4.7.2" in the "TargetFrameworks" property of your project file and then re-run NuGet restore.
SQLite is a great little database for all kinds of personal data storage. Not only does it have drivers for all current programming languages, but it also works without the hassle of creating a server to host it. Today I give you a quick overview on 3 no-code tools to explore your SQLite databases.
Visual Studio 16.9 introduced a bug that prevents us from debugging T4 templates. The debugger rushes to the end of the template and fails with this message:
FileLoadException: Could not load file or assembly 'Microsoft.VisualStudio.Validation, Version=16.8.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
I am a big fan of the XML documentation comments in C#. This documentation is directly in the code and has therefore the biggest chance to be updated when the code changes.
However, when you demand to document all public methods, you end up with a lot of repetitive documentation. As with duplicated code, you will update only the parts you remember, and the others will be outdated in no time. That quickly negates the benefits of having the documentation in the first place.
Last week I run intro an annoying little problem with the ASP.Net MVC 5 template. I created a new MVC web application for .Net 4.8 and after updating the packages it looked like this:
ASP.NET Core Identity offers you a little interface called IEmailSender to wire up your own logic to send emails for account confirmation and password recovery. The official tutorial at Microsoft uses SendGrid for those emails. While this service has certainly its place, we do not want to change our email infrastructure just because we only can find tutorials for SendGrid.
It is time for a little celebration: In the last hours of March my blog hit the 1,000,000 page views milestone:
