In the past we always had often problems to manage logging mechanisms in unit tests, so I wrote ThrowAwayLogger that solves the problem.
1// field
2private ILogger _log = new ThrowAwayLogger();
3
4// call
5_log.Log(LogLevel.Information, _ex, "Test " + _message);
6}
In principle, all this can be implemented via Moq , but there are often cases where validations are not necessary and a simple mock mechanism is sufficient.
Related articles
Dec 14, 2021 - 1 min read
.NET Updates Dezember 2021
Heute hat Microsoft die .NET Updates von Dezember 2021 auf ihrem Blogpost veröffentlicht. Fix CVE-2021-43877: ASP.NET Core Information …
Dec 04, 2021 - 2 min read
Check for .NET NuGet Updates via dotnet outdated cli tool
.NET now has a very powerful CLI that can also handle NuGet packages very well. But one important feature is missing: check if there are …
Nov 11, 2021 - 8 min read
DateTime vs DateTimeOffset - der richtige Umgang mit Zeiten in .NET
Dieser Artikel behandelt den korrekten Umgang sowie Best Practises und Empfehlungen von Datums- und Zeitinformationen, Zeitzonen und …
BEN ABT
Ben is Chief Engineering Officer and Principal Software Engineer at Medialesson.de, with a strong focus on .NET and Microsoft Azure. In his professional role, he designs and builds highly scalable platforms for hybrid and cloud-based scenarios. He also advises companies and C-levels on migrating to the sovereign cloud.
He runs myCSharp.de, the largest and most active German-speaking C# community forum, actively contributes to both his own and external open-source projects and regularly shares his knowledge through his blog, at community events, conferences and as a writer for technical magazines.
Let's Work Together
Looking for an experienced Platform Architect or Engineer for your next project? Whether it's cloud migration, platform modernization or building new solutions from scratch - I'm here to help you succeed.