[Rider] Selecting net10 creates a net9 project
Current behavior 🐛
New project, no changes. Starts in Desktop mode, doesn't start in WebAssembly.
Repro: https://github.com/codymullins/sundy-uno
Expected behavior 🎯
A fresh project should work correctly.
How to reproduce it (as minimally and precisely as possible) 🔬
No response
Workaround 🛠️
No response
Renderer 🎨
- [x] Skia
- [ ] Native
Affected platforms 📱💻🖥️
No response
Uno.Sdk version (and other relevant versions) 📦
No response
IDE version 🧑💻
JetBrains Rider 2025.3 Build #RD-253.28294.88, built on November 10, 2025
Anything else we need to know? 💬
No response
@codymullins Thanks for the report. This is generally caused by missing .NET Workloads.
Can you run the following in your csproj folder:
dotnet workload list
Thanks!
Also, since it's a net9 project, the wasm-tools-net9 should be installed. This is a recent behavior that we're noticing with net9 back compat.
Try running dotnet workload install wasm-tools-net9 in your csproj folder and try again.
That's odd. I selected .NET 10 in Rider for the version to use. Let me update and verify again.
We're looking into this invalid selection, but in the meantime, you can manually change net9.0 to net10.0 in the csproj, that should get you going.
https://github.com/user-attachments/assets/a4415eac-038e-417d-9af5-34cf396cbc87
I upgraded to .NET 10 and it works.
Observation: dev server fails to connect, and presumably, this hides the executable window and pops rider back open. I remember this happening before and found it quite annoying. It seems to happen mostly every time. I caught it on recording where it happens the 2nd time.
https://github.com/user-attachments/assets/18f21905-5938-4839-8848-d8a68b552a6a