PR Summary

There is an edge case when testing binary modules on Linux, where we get into the code path

if (string.Equals(psHome, dir, StringComparison.OrdinalIgnoreCase) ||
   (alternateDirToCheck != null && string.Equals(alternateDirToCheck, dir, StringComparison.OrdinalIgnoreCase)))
   {
        // The ps1xml file no longer exists in $PSHOME.  Downstream, we expect a resolved path,
        // which we can't really do b/c the file doesn't exist.
        fixedFileName = psHome + "\\" + s);
    }

The fix is

    fixedFileName = Path.Combine(psHome, s);

This causes the module load to fail because the engine tries to load types and formats from somepath/bin\Module.formats.ps1xml. Note the backslash.

PR Context

I've only seen this in unit tests hosting PowerShell, hosting powershell.

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge. If this PR is a work in progress, please open this as a Draft Pull Request and mark it as Ready to Review when it is ready to merge.
• Breaking changes
  • None
  • OR
  • Experimental feature(s) needed
    • Experimental feature name(s):
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed