You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've recently migrated most of my nuget packages / oss projects to using PolySharp - I can set language=latest and still target .NET Standard 2.0 - it's great.
It's particularly essential for .NET 8 features, such as annotating for trimming/etc.
<!--Polyfill language features for .NET Standard 2.0 et all, generating internal
items only for the compiler. Enables langversion=latest-->
<PackageReference Include="PolySharp" Version="1.*">
<PrivateAssets>all</PrivateAssets>
<IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
</PackageReference>
The only issue I've had with the library is that since it generates internal stuff, InternalsVisibleTo can cause duplications if there is both a mismatch on targeted frameworks and the consuming (typically unit test) project also includes it unnecessarily. Easily avoided, though.
The text was updated successfully, but these errors were encountered:
I've recently migrated most of my nuget packages / oss projects to using PolySharp - I can set language=latest and still target .NET Standard 2.0 - it's great.
I've recently migrated most of my nuget packages / oss projects to using PolySharp - I can set language=latest and still target .NET Standard 2.0 - it's great.
It's particularly essential for .NET 8 features, such as annotating for trimming/etc.
In Tomlyn.props, add
And
The only issue I've had with the library is that since it generates internal stuff, InternalsVisibleTo can cause duplications if there is both a mismatch on targeted frameworks and the consuming (typically unit test) project also includes it unnecessarily. Easily avoided, though.
The text was updated successfully, but these errors were encountered: