<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>.NET Core on Alessio Franceschelli</title><link>https://alessio.franceschelli.me/categories/dotnet-core/</link><description>Recent content in .NET Core on Alessio Franceschelli</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><copyright>© 2026 Alessio Franceschelli</copyright><atom:link href="https://alessio.franceschelli.me/categories/dotnet-core/index.xml" rel="self" type="application/rss+xml"/><item><title>How to test logging when using Microsoft.Extensions.Logging</title><link>https://alessio.franceschelli.me/posts/dotnet/how-to-test-logging-when-using-microsoft-extensions-logging/</link><pubDate>Mon, 27 Jan 2020 00:00:00 +0000</pubDate><guid>https://alessio.franceschelli.me/posts/dotnet/how-to-test-logging-when-using-microsoft-extensions-logging/</guid><description>&lt;p&gt;Logs are a key element for diagnosing, monitoring or auditing the application&amp;rsquo;s behaviour, so if you are either a library author or you are developing an application, it is important to ensure that the right logs are generated.&lt;/p&gt;
&lt;p&gt;Would it be nice if there was an easy solution to write tests for it?
Let&amp;rsquo;s start a journey through the best approaches to tests logs when using &lt;a href="https://www.nuget.org/packages/Microsoft.Extensions.Logging/" target="_blank" rel="noreferrer"&gt;Microsoft.Extensions.Logging&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Build a .NET library with GitHub Actions</title><link>https://alessio.franceschelli.me/posts/dotnet/build-a-dotnet-library-with-github-actions/</link><pubDate>Wed, 04 Dec 2019 00:00:00 +0000</pubDate><guid>https://alessio.franceschelli.me/posts/dotnet/build-a-dotnet-library-with-github-actions/</guid><description>&lt;p&gt;GitHub Actions are a great free tool to have continuous integration of your opensource .NET library for free, directly into GitHub, saving you from setting up other tools and linking accounts.
Setting it up can feel a daunting task but, if you follow this guide you are going to be able to set it up in 10 minutes!&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://alessio.franceschelli.me/posts/dotnet/build-a-dotnet-library-with-github-actions/feature.png"/></item><item><title>Should I use global.json?</title><link>https://alessio.franceschelli.me/posts/dotnet/should-i-use-global-json/</link><pubDate>Mon, 27 May 2019 00:00:00 +0000</pubDate><guid>https://alessio.franceschelli.me/posts/dotnet/should-i-use-global-json/</guid><description>&lt;p&gt;I often get asked if it is better to have a global.json in a .NET project (not necessarily .NET Core) to define a specific .NET Core SDK version and, unfortunately, if you need a short answer you will get from me the typical engineer answer: it depends!
Here is the full answer so you can decide what suits best for your needs.&lt;/p&gt;</description></item><item><title>HttpClientLab</title><link>https://alessio.franceschelli.me/posts/dotnet/httpclientlab/</link><pubDate>Wed, 19 Dec 2018 00:00:00 +0000</pubDate><guid>https://alessio.franceschelli.me/posts/dotnet/httpclientlab/</guid><description>&lt;p&gt;&lt;em&gt;HttpClientLab turns the HttpClientFactory into a lab, so you can mock the HttpClient to write tests.&lt;/em&gt;&lt;/p&gt;</description></item></channel></rss>