3 ms·
To be fair, I went to the website and gave it a fresh try again: https://platform.uno/docs/articles/get-started-rider.html?tabs=macos#prerequisites https://pla
by StevePerkins 4y ago
To be fair, I went to the website and gave it a fresh try again:
https://platform.uno/docs/articles/get-started-rider.html?tabs=macos#prerequisites https://platform.uno/docs/articles/get-started-rider.html?ta...
I was able to get through the .NET install, and "uno-check" process without much issue.
However, the screenshots on this page show a Solution file with a "MyApp.macOS" project inside. I generated the "MyApp" skeleton project using the verbatim bootstrap command "dotnet new unoapp -o MyApp"... but the generated solution does not include a "MyApp.macOS" project inside.
After a lot of experimenting, I discovered that the WASM-based implementation actually does run. Even though it requires me to enter my root password every time it starts the development HTTP server (WTF?).
I mean... a fresh install, following the published instructions step-by-step verbatim, should produce a "Hello World" skeleton project that matches the doc. Just saying.