зеркало из https://github.com/DeGsoft/maui-linux.git
ea56c4a1b0
Fixes: https://dev.azure.com/devdiv/DevDiv/_workitems/edit/1413769 Fixes: https://github.com/dotnet/maui/issues/3967 Adding a new class to `Platforms\Android` results in: <ItemGroup> <_MauiCompileToAdd Remove="Platforms\Android\AnotherAndroid.cs" /> </ItemGroup> <ItemGroup> <None Include="Platforms\Android\AnotherAndroid.cs" /> </ItemGroup> That's weird! There might be an IDE / ProjectSystem here, but I think we should change the MSBuild includes to workaround this problem. Reviewing the existing `.targets`: 1. We don't need to add `.cs` files to `@(None)`? It doesn't not appear that `dotnet new console` adds `.cs` files to `@(None)`. 2. We can completely get rid of `@(_MauiCompileToAdd)` and just add files to `@(Compile)` directly. After these changes, a `dotnet new maui` app still works. And when I add new `.cs` files in a `Platforms\*\` folder, the `.csproj` file remains unchanged. Yay! |
||
---|---|---|
.. | ||
Microsoft.Maui.Controls.Compatibility.AppLinks.nuspec | ||
Microsoft.Maui.Controls.Compatibility.GTK.nuspec | ||
Microsoft.Maui.Controls.Compatibility.Maps.GTK.nuspec | ||
Microsoft.Maui.Controls.Compatibility.Maps.WPF.nuspec | ||
Microsoft.Maui.Controls.Compatibility.Maps.nuspec | ||
Microsoft.Maui.Controls.Compatibility.Visual.Material.nuspec | ||
Microsoft.Maui.Controls.Compatibility.Visual.Material.targets | ||
Microsoft.Maui.Controls.Compatibility.WPF.nuspec | ||
Microsoft.Maui.Controls.Debug.targets | ||
Microsoft.Maui.Controls.DefaultItems.props | ||
Microsoft.Maui.Controls.DefaultItems.targets | ||
Microsoft.Maui.Controls.DualScreen.nuspec | ||
Microsoft.Maui.Controls.MultiTargeting.targets | ||
Microsoft.Maui.Controls.SingleProject.props | ||
Microsoft.Maui.Controls.SingleProject.targets | ||
Microsoft.Maui.Controls.props | ||
Microsoft.Maui.Controls.targets | ||
Microsoft.Maui.Core.props | ||
Microsoft.Maui.Core.targets | ||
Microsoft.Maui.Resizetizer.targets | ||
Microsoft.Maui.TestUtils.DeviceTests.Runners.targets | ||
_._ | ||
proguard.cfg |