vscode-powershell: Using enableProfileLoading to modify PSModulePath does not persist.

OK this might be caused by PS Core:

if (!string.IsNullOrEmpty(currentProcessModulePath) &&
    NeedToClearProcessModulePath(currentProcessModulePath, personalModulePath, sharedModulePath, runningSxS))
{
    // Clear the current process module path in the following cases
    //  - start sxs ps on windows [machine-wide env:PSModulePath will influence]
    //  - start sxs ps from full ps
    //  - start sxs ps from inbox nano/iot ps
    //  - start full ps from sxs ps
    //  - start inbox nano/iot ps from sxs ps
    currentProcessModulePath = null;
}

You don’t normally see this problem in PS Core but with the VSCode extension, PS Core is started, a script is run to import and start PSES. At this point the env var is correct. However,once PSES starts executing it has to set up its PSHost UI and I “think” in the process of doing that, the above code is executed which resets the PSModulePath. I haven’t had a chance to verify this yet in the debugger. It’s a theory at this point. If this is the case, perhaps we can stash and restore the PSModulePath in PSES.

Is that directory a junction/mount point or anything else weird like that? The other thing that would be good to know is if this happens in pure PowerShell Core - no VSCode.

Are you sure you modifying the profile in Documents\PowerShell instead of the one in Documents\WindowsPowerShell? I can’t repro this with PS Core 6.0.0-rc.

BTW, init script has been discussed here #190 and #880.