Why do we need to remove then re-include the non-.py file extensions?

In MSBuild you can't change an "Include" on an Item as that's it's ID. In order to modify the "Include", you need to remove the whole Item, and then readd it with the updated value.

hmm, I'm a bit worried about this here as we would be potentially exposed to any change of this list in a future arcade update. I wonder if with a bit more code but we could just instead calculate on the fly what the Include value is based on searching for .py, and then adding it back but replacing the .py with empty string would work?

Let me know if you want me to work on the above

I think a more maintainable solution would be for us to get arcade updated to support this scenario. Similar to Do not sign .js files by default (dotnet/arcade#15760).

cc @ellahathaway

I've opened Add support to disable signing python files (dotnet/arcade#16319) for this request.

What's the SLA for things like this plus us taking a new arcade version (that we frequently revert?)

In MSBuild you can't change an "Include" on an Item as that's it's ID. In order to modify the "Include", you need to remove the whole Item, and then readd it with the updated value.

Are you sure about that? AFAIU, with the ; the items will get split up, and they will become individual items. What do you get if you print the items with %(Identity)?

Good call @radical. I tested it in an isolated csproj:

    <ItemGroup>
        <FileExtensionSignInfo Include=".ps1;.psd1;.psm1;.psc1;.py" Foo="bar" />
        <FileExtensionSignInfo Remove=".py" />
    </ItemGroup>

    <Target Name="PrintInfo" BeforeTargets="Build">
      <Message Importance="High" Text="FileExtensionSignInfo items:" />
      <Message Importance="High" Text="  @(FileExtensionSignInfo->'%(Identity) - %(Foo)')" />
    </Target>

Produces