MSBuildLocator.QueryVisualStudioInstances returns empty collection

I was going to analyze one of my projects and hit a wall right at the first step.

MSBuildLocator.IsRegistered is false and MSBuildLocator.QueryVisualStudioInstances returns an empty collection.

I read some questions, answers and articles on the Internet and still have no answer why. What should I fix in my project to receieve a non-empty collection from MSBuildLocator.QueryVisualStudioInstances?

Here is my project

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net6.0</TargetFramework>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.Build.Locator" Version="1.5.5" />
  </ItemGroup>
</Project>

And here is my code:
using Microsoft.Build.Locator;

if (!MSBuildLocator.IsRegistered)
{
    var vs2022 = MSBuildLocator.QueryVisualStudioInstances().Where(x => x.Name == "Visual Studio Community 2022").First();
    MSBuildLocator.RegisterInstance(vs2022); // register the selected instance
}

Update:

It seems I reproduce the issue:

In this situation, the issue comes from my launchsettings.json.

The app on my side is C# console app, and the worked content is:

{
  "profiles": {
    "MyConsoleApp": {
      "commandName": "Project"
    }
  }
}

Based on this launchsettings.json, I am able to get the collection with no-empty.

Original Answer:

I think why it returned empty is because it should be empty in this situation. You filter them, and no matches.

For details, please list all of them and check what they are:

var allInstances = MSBuildLocator.QueryVisualStudioInstances().ToList();

On my side, I didn't see any item's Name matches the "Visual Studio Community 2022".

I can see these:

So I do this:

var latestVersionInstance = MSBuildLocator.QueryVisualStudioInstances().Where(x => x.Name == ".NET Core SDK").First();

And it passed.

In my case the cause was simple: I didn't install .NET 6 SDK. I was under the impression that installing Visual Studio is enough. But it is not enough.