Several packages are rather old - consider upgrading to newer versions

[NikolaMilosavljevic]

There are some very old packages used by the build.

Microsoft.Extensions.FileSystemGlobbing - version 2.0.0

This is very old version, from 2017. It seems that most other projects in .NET are using version 6.0.0, which is also most downloaded from NuGet.org.

Microsoft.Build.Framework - version 16.0.461
Microsoft.Build.Utilities.Core - version 16.0.461

These versions are also rather old, from 2019.

[Evangelink]

@MarcoRossignoli I recall you were doing something regarding FileSystemGlobbing for some SDK insertion. Is it related? Can we safely update?

Regarding the Microsoft.Build.*, I am afraid they are similar to Newtonsoft.Json and are dependencies that can be affecting user tests (@nohwnd can you confirm?). If that's the case we will need to discuss when is a good time to introduce this "breaking change".

[Evangelink]

Ping @nohwnd @MarcoRossignoli

[MarcoRossignoli]

@MarcoRossignoli Marco Rossignoli FTE I recall you were doing something regarding FileSystemGlobbing for some SDK insertion. Is it related? Can we safely update?

Mmm I don't recall nothing related to the FileSystemGlobbing actually.

[MagicAndre1981]

After installing the .NET 9 SDK I was confused that Newtonsoft.Json.dll is Version 13.0.1 in C:\Program Files\dotnet\sdk\9.0.100\TestHostNetFramework. It is confusing that this older version is defined.

Why is this condition added?

<NewtonsoftJsonVersion>13.0.1</NewtonsoftJsonVersion>
<NewtonsoftJsonVersion Condition="'$(DotNetBuildSourceOnly)' == 'true'">13.0.3</NewtonsoftJsonVersion>

[nohwnd]

This is for source build, we try to update the packages, but every time there are bugs as result of that, or the packages no longer support that tfms we are targeting to allow out of life frameworks to run under VS. I would like to straighten this so we can update at least vstest.console and collector to the latest, but there is currently no capacity for this.