Microsoft.Testing.Extensions.TrxReport version 2.0.0 is giving exception

[HakamFostok]

Here is an interesting bug

Setup

<PackageReference Include="TUnit.Playwright" Version="0.67.10" />
<PackageReference Include="Microsoft.Testing.Extensions.TrxReport" Version="1.9.0" />

Everything is ok.

Update the Microsoft.Testing.Extensions.TrxReport package to 2.0.0 version,
and the tests will fail.
Here is the error from the output window

========== Starting test run ==========
========== Test run aborted: 0 Tests (0 Passed, 0 Failed, 0 Skipped) run in 6.8 sec ==========
[Troy.WebApp.UITests.dll] Unhandled exception. System.TypeLoadException: Could not load type 'Microsoft.Testing.Platform.Extensions.TestHost.IDataConsumer' from assembly 'Microsoft.Testing.Platform, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.
   at Microsoft.Testing.Platform.MSBuild.MSBuildExtensions.AddMSBuild(ITestApplicationBuilder builder)
   at Microsoft.Testing.Platform.MSBuild.TestingPlatformBuilderHook.AddExtensions(ITestApplicationBuilder testApplicationBuilder, String[] _) in /_/src/Platform/Microsoft.Testing.Platform.MSBuild/TestPlatformExtensions/TestingPlatformBuilderHook.cs:line 11
   at SelfRegisteredExtensions.AddSelfRegisteredExtensions(ITestApplicationBuilder builder, String[] args) in \obj\Debug\net9.0\AutoRegisteredExtensions.cs:line 12
   at TestingPlatformEntryPoint.Main(String[] args) in \obj\Debug\net9.0\TestPlatformEntryPoint.cs:line 13
   at TestingPlatformEntryPoint.<Main>(String[] args)

[thomhurst]

That requires MTP 2.0 which TUnit isn't on yet, so don't upgrade for now.

[HakamFostok]

Yeah, I solved that by staying on 1.9.0,
Just wanted to report that.
Thanks a lot, TUnit is great

[stigrune]

Ran into the same error message but from the Microsoft.Testing.Extensions.CodeCoverage 18.1.0 package.

[samusaran]

Ran into the same error message but from the Microsoft.Testing.Extensions.CodeCoverage 18.1.0 package.

Yeah just downgrade to 18.0.4 and you're set!

[Xen0byte]

a little late to the party, but was just planning to raise a new issue when I found this; looking forward to the update