Once again when will MS fix VS 2022

Lloyd Sheen 1,376 Reputation points
2023-03-14T15:46:18.4+00:00

User's image

So I have now spent another couple of hours trying , pleading with Visual Studio to get it together. Notice the status msg, "All Succeeded" meaning no errors but VS shows errors and I have not been able to get rid of them. Clean, Rebuild, restart VS, reboot windows.

To add to this I have done a search to see where the duplicate is but of course there is no duplicate.

I spend more time fighting with Visual Studio some days rather than using for development.

I know some who read these posts are getting tired of my posts but as you can see VS has no idea what it is doing. Oh and to top it off it executes even though there are "errors".

.NET MAUI
.NET MAUI
A Microsoft open-source framework for building native device applications spanning mobile, tablet, and desktop.
2,861 questions

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Alessandro Caliaro 4,181 Reputation points
    2023-03-14T18:02:10.6633333+00:00

    Visual studio gives a lot of errors also if there aren't. It's a problem.

    You can try to:

    1- close VS

    2- delete bin and obj directories

    3- try to restore the project with "dotnet -restore xxx.sln"

    4- reopen VS and pray

  2. Michael Glover 36 Reputation points
    2023-03-14T20:09:12.7966667+00:00

    You might try deleting the .suo (solution user options) file, reopening the solution, then building.

  3. Rob Caplan - MSFT 5,412 Reputation points Microsoft Employee
    2023-03-21T21:37:44.44+00:00

    Visual Studio gets updated regularly (17.5.3 released today) and addresses feedback provided by users. You can see the list of fixes in the release notes at Issues Addressed in this release of 17.5.3 .

    If you have constructive feedback on VS please post it via the VS Feedback Tool to the VS Developer Feedback site so it can be investigated for a fix. See Report a problem with the Visual Studio product or installer.

    Issues filed to the Feedback site connect directly into the bug database so they can be tracked. Issues posted elsewhere require that somebody else copy them into the database, which can only happen if they are clear and constructive. If somebody else enters it, then your context and ability to follow up and track the issue are lost. In ideal circumstances, the end result will be the same, but filing initially in the right place is more efficient and more sure.

    Constructive feedback includes a clear title, version information, and description of the problem. Include repro steps, the expected behaviour, and how the actual behaviour differs from what you expect. If you're asked for more information then please respond to that - looking at the issues that you have submitted, most were closed for lack of details when you didn't respond to follow up questions.

    Please leave out non-technical asides that distract from the actual problem. They make your post difficult to follow and hard to separate any actual details.

    If you need help rather than providing feedback, then please post constructively here on Q&A. The same guidelines for constructive help apply: please be polite and clear. Use a descriptive title that summarizes the problem. Explain what you're trying to do and what you need help with. Be clear on versions, steps, and actual vs. expected behaviour. If you've already tried to solve the problem, explain what you did and in what way it didn't work.

    See Guidelines for posting a quality question on Microsoft Q&AGuidelines for posting a quality question on Microsoft Q&A

    For MAUI runtime issues the same applies, but the direct route is through the MAUI GitHub repo at https://github.com/dotnet/maui instead of through the VS Feedback tool.

    0 comments