List of Breaking/Planned changes for MSBuild.Locator v2.0

[YuliiaKovalova]

1. Remove extra property AllowQueryAllRuntimeVersions. AllowAllRuntimeVersions from VisualStudioInstanceQueryOptions.cs means the same, but can't clean up immediately due to backward compatibility.
2. There is a request to add a warning message about the possible compatibility issues - sometimes MSBuild that is being loaded is just too old to have modern things. Add warning message about the used MSBuild version #272 & Identify architecture of found MSBuild #130
   Change API to...

class MSBuildLocationResult
{
  public bool IsCompatibleWithCurrentRuntime;
  public MSBuildLocatorWarning[] Warnings;
  public string RootPath;
  public MSBuildDiscoveryType Context;

  public Version Version;
  public Architecture Architecture; 


  public void Register() {}
}

3. Project targeting .NET 6 cannot use Microsoft.Build 17.4.0 nuget package. dotnet/msbuild#8166 - compatibility warning
4. Add some guardrails to MSBuild Locator #254 - can be also a part of compatibility warning section
5. Can we avoid binding redirects since Locator controls binding? #83 - find the way to implement this
6. Add handling for the case described here: [Bug]: Project object can no longer be created if the change wave 17.10 is in use. dotnet/msbuild#9869 (comment)
7. Handle the case for the versions clash: [Bug]: No way to load NuGet.Frameworks into Default ALC dotnet/msbuild#10228

[rainersigwald]

After reading what you wrote above, I added a Version field to the result, which may actually supersede some of the warning stuff.