You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Update maxversiontested so xaml islands can be used in vstest.console.exe #5041
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.
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.
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.
Activity
nohwnd commentedon May 20, 2024
Would you post a PR for this please?
ChrisGuzak commentedon May 21, 2024
The code in this project is correct.
I'm guessing the ingestion
vstest.console.exeinto the VS installer is not following the same path astesthost.exe. I see the files are in different locations.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)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.
nohwnd commentedon May 21, 2024
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.
nohwnd commentedon Jul 9, 2024
This needs to be solved for the wrapper that Test Explorer owns, information was sent via email because that project is internal.
ChrisGuzak commentedon Mar 13, 2026
Circling back on this after further investigation. The title of this issue is misleading — the wrapper's missing
maxversiontesteddoes not actually affect XAML Islands tests.The process chain is:
The OS checks the process manifest of the exe that hosts XAML, which is
testhost.exe, not the wrapper. Sincetesthost.exealready hasmaxversiontestedfrom PR #4888, XAML Islands tests work fine from the console — verified on VS 18 Preview.The wrapper is still missing
maxversiontestedandlongPathAwarefor consistency, but this is cosmetic / low severity for the XAML Islands scenario that motivated the original issue.