skip to Main Content

Found several similar questions for older VS versions, some especially mentioning C++.
I’m getting the effect with C# as well as VB.Net projects in Microsoft Visual Studio Community 2022 (64-bit) – Version 17.3.3

Steps to reproduce:

  • Open a new VS2022 IDE instance
  • "Create new Project", say type "ASP.Net Core Web App (C#)" or a "Console App (Visual Basic)"
  • Open the View -> "Task List" window
  • Open any code file, e.g. WebApplication1PagesIndex.cshtml.cs
  • In C# add a line
    //TODO: find this in the IDE's "Task List" window // in the OnGet() event handler
    ' Or TODO: something ' in VB.Net code
  • Observed: the TODO line appears in the Task List window as expected //Okay
  • Save, and close the IDE instance
  • Open a the same newly created "WebApplication1" solution in a new VS IDE instance.
  • Observed: Task List window is empty although the TODO line still exists // not Okay
  • As soon as one edits any code file, e,g. WebApplication1PagesError.cshtml.cs, even by just adding and removing a single space
  • Observed: unexpectedly (all if there are more than just one) TODO lines magically reappear in the Task List

Actual question:
Is that a reproducible VS Bug or is it just me / my PC/setup?

3

Answers


  1. Chosen as BEST ANSWER

    Doing a "Visual Studio Installer" -> "Repair" seems to have cured the symptom so far fortunately. (That part took a while though and also demanded an O/S restart. Reinstalling one Extension and arranging desired IDE/Debug windows layout afterwards was easy.)


  2. This also happened to me. I have been using VS 2022 for a while, and today is the first time I’ve seen it. Making a small code edit didn’t change anything, but just closing and restarting VS did.

    I have been clearing caches and cleaning solutions today. I have also had both 2019 and 2022 open, but that hasn’t caused a problem (that I’ve noticed) before.

    Login or Signup to reply.
  3. In the (hidden) .vsProjectEvaluation folder, deleting the older versions of the files .metadata.vx.y and .projects.vx.y of the project in question solved the problem for me.

    Login or Signup to reply.
Please signup or login to give your own answer.
Back To Top
Search