Draft

[Youssef1313]

This is a draft for me to see if there is test coverage for this check, and what it exactly affects.

[Youssef1313]

@baronfel @dsplaisted There are no test failures here, and it's not yet clear to me what scenario breaks. Can we please have a clear test coverage so that we understand the impact?

The check so far doesn't make much sense to me. Part of the condition is:

'$(SelfContained)' == 'true' or
   ('$(_IsPublishing)' == 'true' and
      (
        '$(PublishReadyToRun)' == 'true' or
        '$(PublishSingleFile)' == 'true' or
        '$(PublishAot)' == 'true'
      )
   )

I don't think users will try to publish VSTest test projects that way, and I feel that a break here in .NET 10 to help us move forward with proper MTP support is fine. In a very rare case where a user is impacted, I think they should explicitly set UseCurrentRuntimeIdentifier in their VSTest project themselves, instead of the SDK trying to magically hack around stuff and breaking MTP.