dotnet / maui

.NET MAUI is the .NET Multi-platform App UI, a framework for building native device applications spanning mobile, tablet, and desktop.
https://dot.net/maui
MIT License
21.99k stars 1.72k forks source link

Upgrade fails, conflicting messages on installed vs needed #21825

Closed fasteddys closed 5 months ago

fasteddys commented 5 months ago

Description

Hello I am using the Weight tracker, F1, MauiPets sample and upgraded the project using the docs.

From the below picture you can see the conflicting messages.

While Visual Studio says I need to INSTALL the frameworks, and ask me to install. The installer complains that its ALREADY installed??

I have clear MEF cache, rebooted and several other things, but no help

image

Steps to Reproduce

Download F1 wight tracker or Maui Pets tried both options, run the upgrade assistant. Also manual update VS complains about missing SDK But installer claims they are there

image

Link to public reproduction project repository

Link to F1, Maui Pets,

Version with bug

8.0.3 GA

Is this a regression from previous behavior?

Yes, this used to work in .NET MAUI

Last version that worked well

6.0

Affected platforms

iOS, Android, Windows, Other (Tizen, Linux, etc. not supported by Microsoft directly)

Affected platform versions

No response

Did you find any workaround?

No response

Relevant log output

No response

dotnet-policy-service[bot] commented 5 months ago

Thanks for the issue report @fasteddys! This issue appears to be a problem with Visual Studio, so we ask that you use the VS feedback tool to report the issue. That way it will get to the routed to the team that owns this experience in VS.

If you encounter a problem with Visual Studio, we want to know about it so that we can diagnose and fix it. By using the Report a Problem tool, you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks.

  1. Go to the Visual Studio for Windows feedback tool or Visual Studio for Mac feedback tool to report the issue
  2. Close this bug, and consider adding a link to the VS Feedback issue so that others can follow its activity there.