<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Polysharp on It Must Be Code!</title><link>https://itmustbecode.com/tags/polysharp/</link><description>Recent content in Polysharp on It Must Be Code!</description><generator>Hugo</generator><language>en-CA</language><lastBuildDate>Fri, 20 Jan 2023 03:30:30 +0000</lastBuildDate><atom:link href="https://itmustbecode.com/tags/polysharp/feed.xml" rel="self" type="application/rss+xml"/><item><title>Dataverse Plugins : Unlock the latest C# features with PolySharp</title><link>https://itmustbecode.com/dataverse-plugins-unlock-the-latest-c-features-with-polysharp/</link><pubDate>Fri, 20 Jan 2023 03:30:30 +0000</pubDate><guid isPermaLink="false">https://itmustbecode.com/dataverse-plugins-unlock-the-latest-c-features-with-polysharp/</guid><description>&lt;p&gt;Whenever a new version of C# is released I&amp;rsquo;m always eager to explore the new features of the language. However, as a Power Platform developer, it can be frustrating knowing that they can&amp;rsquo;t be used to develop Dataverse plugins, which constitutes a significant part of my daily work.&lt;/p&gt;
&lt;p&gt;As a matter of fact, due to a dependency on the Microsoft CRM SDK, Dataverse plugins are confined to use an older version of the .NET framework (4.6.2) which natively supports C#7.3, while the latest version is C# 11.&lt;/p&gt;</description></item></channel></rss>