Skip to content

Upgrading Microsoft.NET.Test.Sdk 17 to 18

Breaking17.14.1 → 18.11.0Breaking6Security1Deprecated1New9Changed32Fixed41Other147

Full comparisonBack to Microsoft.NET.Test.Sdk
BreakingUpgrade verdict

6 breaking changes and a security fix.

In plain terms
  • Removes tpv0.
  • The MSTest.Assert.Extensions package is no longer provided.
  • Removes fakes v1 from FakesUtilities.
  • Tests that target .NET Framework can no longer run on non-Windows systems through a Mono fallback; they must run on Windows.
Must act Top 5 of 8 that need code or config changes

Target frameworks requirement changed in 18.9.0: .NETFramework4.6.2, native0.0, net8.0 → .NETFramework4.6.2, net8.0.

What you must change

Breaking6
Removes tpv0.
tpv0
18.0.0GitHub ReleaseSummarizedView source
Removes MSTest.Assert.Extensions.
MSTest.Assert.Extensions
18.0.0GitHub ReleaseSummarizedView source
Removes fakes v1 from FakesUtilities.
FakesUtilities
18.0.0GitHub ReleaseSummarizedView source
Drops the Mono fallback and runs .NET Framework tests on Windows only.
18.10.0GitHub ReleaseSummarizedView source
Removes the experimental test session feature.
18.10.0GitHub ReleaseSummarizedView source
Removes CUIT (Coded UI Test) from NuGet packages and test projects.
18.0.0GitHub ReleaseSummarizedView source
Security1
Restricts artifact temp directory permissions on Unix.
18.8.0GitHub ReleaseSummarizedView source

Deprecations to plan for

Deprecated1
Deprecates EnableShutdownAfterTestRun, which is a no-op.
EnableShutdownAfterTestRun
18.6.0GitHub ReleaseSummarizedView source