search

Redth / dotnet-maui-check

.NET MAUI Check tool
MIT License
479 stars 79 forks source link

Maui check failed to update #51

Closed AhmedHemdan21 closed 3 years ago

AhmedHemdan21 commented 3 years ago

After updating to .NET 6 preview 5 I tried to run maui-check command and it showed `

Updating to version 0.5.6 or newer is required:

dotnet tool update --global Redth.Net.Maui.Check, then when I run the update command I get this error

Tool 'redth.net.maui.check' failed to update due to the following: Failed to uninstall tool package 'redth.net.maui.check': Access to the path 'C:\Users\Ahmed\.dotnet\tools.store\redth.net.maui.check\0.4.2' is denied.

Also, I tried to run dotnet tool uninstall --global Redth.Net.Maui.Check but I get the same error.

elOG8 commented 3 years ago

I have the same problem.... any news?

Fabi commented 3 years ago

Worked for me when I run it as admin 🤔

AhmedHemdan21 commented 3 years ago

Worked for me when I run it as admin 🤔

I tried with admin privilege using Windows Terminal, Command Prompt, and PowerShell and I get the same issue. @Fabi did you have a previous version installed or is this a fresh install?

ncarandini commented 3 years ago

Please try to close any istance of VS Code or VS that may use the folder. Worst case scenario, reboot 😄 I solved closing all istances of VS Code. I found it when I tried to delete the folder by myself from the file Explorer. It refused to delete it telling me that it was used by someone...

AhmedHemdan21 commented 3 years ago

Please try to close any instance of VS Code or VS that may use the folder. Worst case scenario, reboot 😄 I solved closing all instances of VS Code. I found it when I tried to delete the folder by myself from the file Explorer. It refused to delete it telling me that it was used by someone...

Thanks for your suggestion, I tried everything from restarting the device (around 9 times), Windows system restore (3 times), trying to uninstall .NET SDK which was a total nightmare to do so. Finally, deleting the SDK files manually and repairing VS 2022 did solve the issue, so it seems that installing VS 2022 with .NET SDK at the same time caused lots of issues.