Stride Game Studio is looking for the Xamarin.Android.CSharp.targets file under the wrong path

[paskaler]

Release Type: Official Release
Version: 4.1.0.1459-beta

Platform(s): Windows 10 20H2, Microsoft .NET Core Runtime 5.0.203

Describe the bug
An Android project cannot be created due to the following error:
Error: The imported project "C:\Program Files\dotnet\sdk\5.0.203\Xamarin\Android\Xamarin.Android.CSharp.targets" was not found. Confirm that the expression in the Import declaration "C:\Program Files\dotnet\sdk\5.0.203\\Xamarin\Android\Xamarin.Android.CSharp.targets" is correct, and that the file exists on disk.

Steps to reproduce the behavior:

1. Lunch the Stride Launcher 5.1 on your PC
2. Set the current version to 4.1.0.1459 and open the Stride 3D Game Studio 4.1.0.1459-beta (.NET 5.0.6)
3. Navigate to a "New game" and select only an Android platform option
4. Press OK

Expected behavior
Xamarin.Android.CSharp.targets file is not part of the .NET Core installation folder. MSBuild is installed in a folder under each version of the Visual Studio.

Installation folder for VS 2019 Community Edition
c:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Xamarin\Android\Xamarin.Android.CSharp.targets

Screenshots

Additional context
I have not tried to create a project on other platforms and this must be also included in the further investigation.

[sak9188]

same issue

[MeharDT]

This seems to have been fixed for Android but I'm able to replicate this issue for iOS in Stride 4.1.0.1898 on two different dev environments.

Does anyone know which PR this was fixed in?

[Doprez]

could have been azeno? releases/4.1.0.1805...releases/4.1.0.1822 I was conveniently looking at release comparisons due to another issue and I saw this lol.

[MeharDT]

Fixed, the iOS csproj template wasn't updated for .NET projects. I'll create a PR shortly, these projects currently don't build within Stride for other reasons that I'm looking into.

This issue can probably be closed as well since the Android platform no longer has this issue.