Xamarin SDK not found
Hi all,
I'm hoping someone can give me some clues re Xamarin project. I've looked at some threads and doco but feel like I'm going around in circles.
After starting a new project from the Xamarin Template, I end up at screenshot 1.
I have Visual Studio 2022 installed, so I then go and check that as per the "use Visual Studio installer instead" advice.
There though, I see that Visual Studio believes everything is installed - screenshot 2.
I've also tested in Visual Studio creating a Xamarin project and can build and compile to the Android emulator, and everything works fine.
What's the missing link to get it to work in Rider?
Please sign in to leave a comment.
Also noted the message about selecting a different MSBuild version. I've attempted to switch back and forth between 16 and 17 - but end up going around in circles there too. I have .NET SDK 6 and 7 installed. If I leave it on the auto-detected setting, I get this error (below screenshot). If I switch it to 17.0, I get the errors in the original screenshots.
Hello,
After you switch the MSBuild version, please try deleting bin/ and obj/ folders from your solution folder, reload the solution and restore NuGet packages once again. Will you observe the same result?
If it does not make a difference, please upload Rider logs collected after opening the problematic solution.
I think I'll give up - have spent way too much time on this. I'll stick with Rider for Unity work only, and do the Xamarin project is VS.
Please accept our apologies for the inconvenience. Use this thread or submit a new support ticket if you need any further assistance with this.
Any fix for this?
Does Rider actually support Linux? I've emailed about this issue (twice last week) and posted on this form about it at length and nothing. As claiming to be a multiplatform IDE without Xamarin support seems kinda silly in 2023 doesn't it?
Hello Xmichael99,
Rider does support Linux, however Xamarin.Android workload is not supported because SDK itself is not officially supported on Linux.
You can find more information about this issue in the legacy article about Xamarin.Android and in RIDER-5747.
Yeah, same problem…
Hello Yinlong Zhao ,
Could you please apply the workaround and if that does not help, provide me with the data my colleague requested above?
Thank you in advance!
Hi! I uploaded the Rider logs in request #5919067, hope it helps!
Any updates on this? Now that Visual Studio for Mac will retire in August 2024… Rider should be a good alternative; however, as this problem is still not solved… we will be looking into other alternatives.
Hello Dsfugabanjr ,
Could you please let me know the.exact issue you are having? Error? Have you tried tweaking Settings | Build, Execution, Deployment | Toolset and Build > MSBuild version?
Looking forward to your response.
Um, hi. I just wanna say, if you are troubled by the “MSBuild is incompatible with .Net SDK” message (just like I am before), you can just leave it there until you meet a real compatibility issue, because that message is just a reminder and don't necessarily mean there is a problem. I have this message showing every time but as far as I am concerned there are no problems at all. Just remember to use the MSBuild corresponding to your mono (under the mono directory)
The exact error is when you select msbuild 17 you cannot load xamarin native projects. When you select msbuild 16 you cannot load xamarin shared project, nore any .net projects. So you 're just stuck with an unbuildable xamarin solution.
The solution to this nonsense is the following:
close rider
% sudo launchctl setenv MSBuildEnableWorkloadResolver false
open rider
Then comes another problem when building. Though i have SDK 16 selected from ……/visualstudio/17/blabla/msbuil.dll I'm getting an error:
Users/xxx/.dotnet/sdk/9.0.100/Containers/build/Microsoft.NET.Build.Containers.targets(210,35): Error MSB4113 : Specified condition "@(PackageReference->AnyHaveMetadataValue('Identity', '$(_ContainersPackageIdentity)'))" evaluates to "" instead of a boolean.
How come rider uses .msbuild 17 from dotnet/sdk/9.0.100 if it was instructed to use msbuild 16.
just deleted folders user/.dotnet/sdk/9..whatever and user/.dotnet/sdk-manifests/9..whatever to pass though this, again, nonsense, to use lower sdks.
Taublast Ru Could you please collect Rider logs and upload them via Upload service or submit a new bug report?