Fix 'runtimeconfig.template.json : warning XA0101: @(Content) build action is not supported' warnings.

[ChristophSchmidpeter]

Fix warnings of the form

runtimeconfig.template.json : warning XA0101: @(Content) build action is not supported

when (initially) building the repository.

[ChristophSchmidpeter]

Is Content -> None correct here, or is Content needed here, and I need to exclude the runtimeconfig.template.json files conditionally for net7.0-android instead?

[edgarfgp]

Is Content -> None correct here, or is Content needed here, and I need to exclude the runtimeconfig.template.json files conditionally for net7.0-android instead?

I think it is ok to set it to None for now. This was introduced to test Avalonia Web support in #124 (I need to tweak that PR to make it work)

[ChristophSchmidpeter]

@edgarfgp I wonder why the build system complains when using Content. But only for Android ( "TargetFramework=net7.0-android" in warning). Having multi-target project nowadays, this seems to be a bug, or no? Or is this warning triggered for good reason? If not, I could open a ticket in e.g. dotnet/runtime

[edgarfgp]

Is Content -> None correct here, or is Content needed here, and I need to exclude the runtimeconfig.template.json files conditionally for net7.0-android instead?

I think it is ok to set it to None for now. This was introduced to test Avalonia Web support in #124 (I need to tweak that PR to make it work)

@edgarfgp I wonder why the build system complains when using Content. But only for Android ( "TargetFramework=net7.0-android" in warning). Having multi-target project nowadays, this seems to be a bug, or no? Or is this warning triggered for a good reason? If not, I could open a ticket in e.g. dotnet/runtime

@ChristophSchmidpeter I think this is because we are using a SingleProject with some MSBuild magic, While AvaloniaUI has a separate project for each platform. So it won't complain on Android or iOS.

[ChristophSchmidpeter]

I see, that sounds most likely. There was some Avalonia single project effort, which might resolve that problem in that case by itself. But that effort seems to be stale at least for now.

I guess using conditions like <ItemGroup Condition="'$(AvaloniaPlatform)' != 'Android'"> or similar might work around the warning on the Web branch in the meantime (unless there is a better way to do so ofc.).