Note regarding the new-api-needs-documentation label:

This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, to please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change.

@eerhardt @rainersigwald can we make that property readable from msbuild as a property function?

• By default, you can only call certain members on certain types – selected to be free of side-effects. Here’s the full list:

from https://devblogs.microsoft.com/visualstudio/msbuild-property-functions/. Sounds to me like we need to "white-list" that property? That information could be outdated as I see that we are reading other properties from RuntimeInformation already:

can we make that property readable from msbuild as a property function?

It is already possible today (since this property is on RuntimeInformation):

  <PropertyGroup>
    <MyRid>$([System.Runtime.InteropServices.RuntimeInformation]::RuntimeIdentifier)</MyRid>
  </PropertyGroup>

  <Target Name="PostBuild"
          AfterTargets="Build">
    <Message Text="Current RID: $(MyRid)" Importance="high" />
  </Target>

On my machine outputs:

  Current RID: win10-x64

However, note that this will only work from MSBuild running on .NET 5 and above, since this API is only available there. It won't work on .NET Core 3.x, nor will it work on MSBuild running on .NET Framework.

Great, thanks!