F5 on a saved script isn't dot sourcing

Prerequisites

• I have written a descriptive issue title.
• I have searched all issues to ensure it has not already been reported.
• I have read the troubleshooting guide.
• I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
• I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.

Summary

Looks like we’re creating a new scope for invocation of script files, leaving any set variables and functions no longer accessible.

PowerShell Version

Name                           Value
----                           -----
PSVersion                      7.2.0-preview.10
PSEdition                      Core
GitCommitId                    7.2.0-preview.10
OS                             Microsoft Windows 10.0.18363
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visual Studio Code Version

1.60.0
e7d7e9a9348e6a8cc8c03f877d39cb72e5dfb1ff
x64

Extension Version

ms-vscode.powershell-preview@2021.11.1

Steps to Reproduce

1. New file
2. Add $a = 50
3. Save it
4. <kbd>F5</kbd>
5. Type $a in the PSIC
6. See it’s not set

Visuals

No response

Logs

No response

[rjmholt]

Probably an oversight. Moving away from dot-sourcing in the API is done for constrained language mode compatibility. In this case (if I’ve read correctly) that doesn’t make sense because the debugger isn’t going to work in CLM. Just remember that anything that dot-sources or uses useLocalScope: false (the default setting) will fail in CLM.

[JustinGrote]

I feel like I called this out earlier that it was using & instead of . in the code.