Open baskren opened 8 months ago
Thanks for the report!
While this is a pworkaround, this is mainly caused by running dotnet build
instead of msbuild
. I don't think that modifying the dotnet build this way is a particularly good way for fixing this... is there an issue by Microsoft that references this particular workaround?
What would you like to be added
I apologize for this edge case but
uno-check
might be a great place to address this issue I have every time the DotNet SDK is upgraded. I'm running Windows for ARM on a MacBookPro (via Parallels --- an officially Microsoft sanctioned way of doing this). After each DotNet SDK upgrade, I get the following error when building from the command line:To fix this, I have to open up an Admin Command Prompt, cd to the latest
C:Program Files\dotnet\sdk\#.#.###\Microsoft
folder, and then do the following:And then everything is good.
Would it be possible for
uno-check
to :VisualStudio
folder is present in theMicrosoft
folder in the currently supported version of dotnet SDK?Thanks for considering this.
Why is this needed
Make adoption of UNO easier for nerds like me.
For which platform
No response
Anything else we need to know?
You guys are the greatest!