Skip to content

Update maxversiontested so xaml islands can be used in vstest.console.exe #5041

Closed

Description

Description

This is a variation of #4887 that I missed when I fix that (that I've verified via updated VS).

vstest.console.exe needs the same manifest update.

but I took a look at the source and see it has been updated. need to investigate further.

Steps to reproduce

see linked issue for repo and details

Activity

  1. nohwnd commented on May 20, 2024

    @nohwnd
    Member

    Would you post a PR for this please?

  2. ChrisGuzak commented on May 21, 2024

    @ChrisGuzak
    MemberAuthor

    The code in this project is correct.

    I'm guessing the ingestion vstest.console.exe into the VS installer is not following the same path as testhost.exe. I see the files are in different locations.

    C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE
        CommonExtensions\Microsoft\TestWindow\vstest.console.exe
        Extensions\TestPlatform\testhost.exe
    

    I also installed these tools using the BuildTools install location and that ended up in a different location from those mentioned above (note the x86)

    C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\Common7\IDE\CommonExtensions\Microsoft\TestWindow\vstest.console.exe
    

    Do you know who owns the VS ingestion process for these binaries? I think we need to ask them why this binary has not kept up with testhost.exe.

  3. nohwnd commented on May 21, 2024

    @nohwnd
    Member

    You've got mail. CommonExtensions\Microsoft\TestWindow\vstest.console.exe is a wrapper of the real vstest.console for backwards compat reasons. It won't have your manifest changes, and so that is why it does not work.

  4. nohwnd commented on Jul 9, 2024

    @nohwnd
    Member

    This needs to be solved for the wrapper that Test Explorer owns, information was sent via email because that project is internal.

  5. ChrisGuzak commented on Mar 13, 2026

    @ChrisGuzak
    MemberAuthor

    Circling back on this after further investigation. The title of this issue is misleading — the wrapper's missing maxversiontested does not actually affect XAML Islands tests.

    The process chain is:

    wrapper vstest.console.exe (TestWindow, .NET Framework shim)
      → real vstest.console.exe (TestPlatform, .NET CoreCLR)
        → testhost.exe (runs test code + XAML)
    

    The OS checks the process manifest of the exe that hosts XAML, which is testhost.exe, not the wrapper. Since testhost.exe already has maxversiontested from PR #4888, XAML Islands tests work fine from the console — verified on VS 18 Preview.

    The wrapper is still missing maxversiontested and longPathAware for consistency, but this is cosmetic / low severity for the XAML Islands scenario that motivated the original issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions