<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Migration on Dimitri Laaraybi</title>
    <link>https://www.dimitrilaaraybi.com/tags/migration/</link>
    <description>Recent content in Migration on Dimitri Laaraybi</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 02 Dec 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.dimitrilaaraybi.com/tags/migration/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Say Hello to .NET 10 !</title>
      <link>https://www.dimitrilaaraybi.com/blog/migratetodotnet10/</link>
      <pubDate>Tue, 02 Dec 2025 00:00:00 +0000</pubDate>
      <guid>https://www.dimitrilaaraybi.com/blog/migratetodotnet10/</guid>
      <description>&lt;h1 id=&#34;introduction&#34;&gt;Introduction&lt;/h1&gt;&#xA;&lt;p&gt;It&amp;rsquo;s been a recurrent meeting every 2 years, as this month Microsoft gave us the chance to try and adopt the new LTS version of our beloved framework, which is .NET 10 🔥&lt;br&gt;&#xA;In this post, I&amp;rsquo;ll show you what are the big new improvements and features in this new LTS version, and also how to migrate your apps, which, you will see, has not changed a lot since the previous versions and this is a pretty good point.&lt;/p&gt;</description>
    </item>
    <item>
      <title>SLNX, the new solution format in .NET ✨</title>
      <link>https://www.dimitrilaaraybi.com/blog/newslnxformat/</link>
      <pubDate>Mon, 14 Apr 2025 00:00:00 +0000</pubDate>
      <guid>https://www.dimitrilaaraybi.com/blog/newslnxformat/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;With .NET 8, Microsoft introduced a new solution file format: &lt;code&gt;.slnx&lt;/code&gt;.   This format aims to improve solution management, making large-scale editing scenarios easier and optimizing performance  for large codebases.&lt;br&gt;&#xA;As mentionned earlier in March in &lt;a href=&#34;https://devblogs.microsoft.com/dotnet/introducing-slnx-support-dotnet-cli/&#34;&#xA;    target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;&#xA;  Chet Husk&amp;rsquo;s post&#xA;&lt;/a&gt; on .NET blog, Microsoft now officially supports it in their latest SDK ! 😎&lt;br&gt;&#xA;Before .NET 9, the only way available to use this new format was to use the &amp;ldquo;Save As&amp;rdquo; feature on an existing .SLN file and target the SLNX format.&lt;br&gt;&#xA;Now new projects can be created by default using this format, which is pretty cool 🥳&lt;/p&gt;</description>
    </item>
    <item>
      <title>No, FluentAssertions is not the only one... Here is how to switch from FluentAssertions to Shouldly !</title>
      <link>https://www.dimitrilaaraybi.com/blog/migratetoshouldly/</link>
      <pubDate>Sun, 02 Mar 2025 00:00:00 +0000</pubDate>
      <guid>https://www.dimitrilaaraybi.com/blog/migratetoshouldly/</guid>
      <description>&lt;h1 id=&#34;introduction&#34;&gt;Introduction&lt;/h1&gt;&#xA;&lt;p&gt;Hey all ! 🫡&lt;/p&gt;&#xA;&lt;p&gt;Let&amp;rsquo;s talk about another little drama that has been shaking the .NET community during the last weeks.&lt;br&gt;&#xA;When working on unit tests in .NET, developers often rely on assertion libraries to make their tests more readable and expressive.&lt;br&gt;&#xA;Two popular libraries in this space are &lt;strong&gt;FluentAssertions&lt;/strong&gt; and &lt;strong&gt;Shouldly&lt;/strong&gt;. While both libraries serve the same purpose, one of them actually updated its licensing model and frightened the whole community about his new goal, making money 😂 (Well who does not want to) &lt;br&gt;&#xA;And this one is &lt;strong&gt;FluentAssertions&lt;/strong&gt;.&lt;br&gt;&#xA;In fact, it now &lt;a href=&#34;https://www.reddit.com/r/dotnet/comments/1i17jm0/fluentassertions_becomes_paid_software_for/&#34;&#xA;    target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;&#xA;  requires a paid licence&#xA;&lt;/a&gt; to be used for commercial use. At least, concerning the 8.x.x version. The developers have stated that the 7.x.x version will be forever free and receive critical fixes, but this strange move from their side may have pushed you to find another library for your assertions, to avoid any problems with the company you work for.&lt;br&gt;&#xA;If that&amp;rsquo;s the case, here is a little tutorial that explains how to migrate from FluentAssertions to Shouldly !&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to migrate your application to .NET 8 ?</title>
      <link>https://www.dimitrilaaraybi.com/blog/migratetodotnet8/</link>
      <pubDate>Wed, 14 Feb 2024 00:00:00 +0000</pubDate>
      <guid>https://www.dimitrilaaraybi.com/blog/migratetodotnet8/</guid>
      <description>&lt;h1 id=&#34;introduction&#34;&gt;Introduction&lt;/h1&gt;&#xA;&lt;p&gt;Hey devs !&lt;/p&gt;&#xA;&lt;p&gt;As you may all know, the new version of .NET, .NET 8, has been released on November 14 2023. A lot of you may have applications still in .NET 6 or earlier.&lt;br&gt;&#xA;The end of support date for .NET 6 is November 12, 2024, so it&amp;rsquo;s good considering migrating your applications right now.&lt;br&gt;&#xA;In this article, we&amp;rsquo;ll see what improvements brings .NET 8, and how to migrate your applications.&lt;br&gt;&#xA;Microsoft has done a good job to make it easy for us to migrate from .NET 6 to .NET 8, or .NET 7 to .NET 8 (at least if you don&amp;rsquo;t rely on a Blazor app&amp;hellip;), so we might as well make the most of it 😁&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to switch from Moq to NSubstitute after the SponsorLink scandal ?</title>
      <link>https://www.dimitrilaaraybi.com/blog/moqtonsubstitute/</link>
      <pubDate>Thu, 17 Aug 2023 00:00:00 +0000</pubDate>
      <guid>https://www.dimitrilaaraybi.com/blog/moqtonsubstitute/</guid>
      <description>&lt;p&gt;Hey devs ! 😁&lt;/p&gt;&#xA;&lt;p&gt;If you are a .NET developer who uses the popular mocking library Moq for your unit tests, you may have heard about the recent controversy that erupted when it was revealed that Moq was secretly collecting and sending user email addresses to a third-party service called SponsorLink. This was done &lt;a href=&#34;https://www.reddit.com/r/dotnet/comments/15ljdcc/does_moq_in_its_latest_version_extract_and_send/&#34;&#xA;    target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;&#xA;  without the consent or knowledge of the developers who used Moq&#xA;&lt;/a&gt;, and raised serious privacy and security concerns.&lt;br&gt;&#xA;In this post, I&amp;rsquo;ll try to explain in more details what this scandal is all about and how to switch from Moq to NSubstitute if you see fit, but also how to prevent your projects from those vulnerabilities in a DevSecOps way 😉&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
