Document MTP v1 to v2 migration #48673
Open
+59
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Youssef1313
requested review from
Evangelink,
nohwnd and
gewarren
and removed request for
a team and
IEvangelist
nohwnd
reviewed
Sep 23, 2025
| Support for target frameworks .NET Core 3.1 to .NET 7 is dropped. The minimum supported .NET version is .NET 8. | ||
| This change doesn't affect .NET Framework. .NET Framework 4.6.2 continues to be the minimum supported .NET Framework target. | ||
|
|
||
| ### Remove obsolete types |
There was a problem hiding this comment.
Suggested change
| ### Remove obsolete types | |
| ### Removed obsolete types |
| 1. VSTest-based implementation: this was the only implementation up to .NET 9 SDK. | ||
| 2. MTP-based implementation: this was added starting in .NET 10 SDK. | ||
|
|
||
| Running MTP test projects with .NET 10 SDK now requires opting-in to the MTP-based `dotnet test` and can no longer be run with the VSTest-based implementation, which was previously enabled by `TestingPlatformDotnetTestSupport` MSBuild property in MTP v1. |
There was a problem hiding this comment.
Would be nice to describe this in more actionable way.
Suggested change
| Running MTP test projects with .NET 10 SDK now requires opting-in to the MTP-based `dotnet test` and can no longer be run with the VSTest-based implementation, which was previously enabled by `TestingPlatformDotnetTestSupport` MSBuild property in MTP v1. | |
| Running MTP test projects with .NET 10 SDK now requires opting-in to the MTP-based `dotnet test` by: | |
| ... the global.json config | |
| Without this opt-in, dotnet test will fail with this error: | |
| `TestingPlatformDotnetTestSupport` MSBuild property is no longer having any effect and can be removed from the project. |
tkapin
reviewed
Sep 23, 2025
gewarren
approved these changes
Sep 24, 2025
| href: ../../core/testing/unit-testing-mstest-migration-v3-v4.md | ||
| - name: Microsoft.Testing.Platform support (MSTest runner) | ||
| href: ../../core/testing/unit-testing-mstest-runner-intro.md | ||
| - name: Migrate from Microsoft.Testing.Platform v1 to Microsoft.Testing.Platform v2 |
There was a problem hiding this comment.
Suggested change
| - name: Migrate from Microsoft.Testing.Platform v1 to Microsoft.Testing.Platform v2 | |
| - name: Migrate from Microsoft.Testing.Platform v1 to v2 |
There was a problem hiding this comment.
Might make it easier to read.
|
|
||
| ### API signature changes | ||
|
|
||
| - A `CancellationToken` parameter was added to `IOutputDevice.DisplayAsync`. |
There was a problem hiding this comment.
Use an xref for IOutputDevice.DisplayAsync?? There's a VS Code extension you can install to help with xrefs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Internal previews