Add more MSTest properties

[gewarren]

• UseWinUI to set to true when testing WinUI UI components. (MSTest)
• EnableMSTestV2CopyResources (default value is true) that allows to copy resources dll to the output (MSTest)
• xUnit is finishing its onboarding so there will be an equivalent property [to EnableNUnitRunner]. I have double checked and xUnit v3+ will be using UseMicrosoftTestingPlatformRunner
• I would also add DisableTestingPlatformServerCapability that removes the project capability used by VS and VS Code Test Explorers to know which platform protocol to use (VSTest or Microsoft.Testing.Platform). Note that at the moment, the Microsoft.Testing.Platform is not yet available publicly but will be soon.
• GenerateTestingPlatformConfigurationFile is only available when IsTestingPlatformApplication is true and is used to allow the copy and rename of the config file in the output folder.
• I am wondering if it would make sense to group the properties by platform, VSTest and Microsoft.Testing.Platform, to make it easy to understand which properties are available in which mode.

Originally posted by @Evangelink in #42404 (comment)

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: cb4428fc-215c-78e1-5ff0-fe73f7a08260
• Version Independent ID: 6741b1de-38a4-fbb1-d79d-acc47d549a2d
• Content: MSBuild properties for Microsoft.NET.Sdk - .NET
• Content Source: docs/core/project-sdk/msbuild-props.md
• Service: dotnet-fundamentals
• GitHub Login: @gewarren
• Microsoft Alias: gewarren

---

Associated WorkItem - 417525

[gewarren]

@Youssef1313 Any interest in taking this one?

[Youssef1313]

@gewarren Sorry I didn't notice this one earlier but came across it by chance today.

• I personally don't feel like UseWinUI is something to be documented for MSTest.

• I also don't know under what scenario a user will want to set EnableMSTestV2CopyResources to false. So can't say much about this one.

• UseMicrosoftTestingPlatformRunner is briefly mentioned here. But I think we could expand it yes.

• For DisableTestingPlatformServerCapability, my understanding is that it's mostly used as a temporary workaround for Test Explorer issues. So I'm not really sure whether or not it should be documented.

• So far I never seen a scenario where a user will want to set GenerateTestingPlatformConfigurationFile to false, but it could still be reasonable to document.

• For grouping properties by testing platform (VSTest/MTP), I totally agree. I have already seen cases where there was confusion about GenerateProgramFile property (which is VSTest-specific), and some users were expecting it to have an effect for MTP.