Recent work to annotate multi-TFM libraries for linker safety has introduced netcoreapp specific #ifdefs in ref assemblies, e.g. in System.Text.Json, in order to use DynamicallyAccessedMembersAttribute and DynamicallyAccessedMemberTypes which are netcoreapp only. From previous discussions on keeping support for netstandard2.0 TFMs, whenever we have a situation that requires adding #ifdefs in the ref, it introduces increased complexity in maintaining support for ns2.0.
Similar to the approach for Nullable and the Microsoft.Extension libraries, the action for 5.0 is to use internal versions of the attributes as a dependency on each applicable library.
cc @eerhardt @joperezr @ericstj
fyi @ahsonkhan
Recent work to annotate multi-TFM libraries for linker safety has introduced netcoreapp specific #ifdefs in ref assemblies, e.g. in System.Text.Json, in order to use
DynamicallyAccessedMembersAttributeandDynamicallyAccessedMemberTypeswhich are netcoreapp only. From previous discussions on keeping support for netstandard2.0 TFMs, whenever we have a situation that requires adding #ifdefs in the ref, it introduces increased complexity in maintaining support for ns2.0.Similar to the approach for Nullable and the Microsoft.Extension libraries, the action for 5.0 is to use internal versions of the attributes as a dependency on each applicable library.
cc @eerhardt @joperezr @ericstj
fyi @ahsonkhan