Unable to load Az modules - Assembly with same name is already loaded

[wsmelton]

Prerequisites

• I have written a descriptive issue title.
• I have searched all open and closed 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.
• If this is a security issue, I have read the security issue reporting guidance.

Summary

If you load a PowerShell file that has references to Azure PowerShell commands the assemblies are being loaded without loading the module fully.

This is repeat of #3012 which was closed with no solution. Extensions do not matter in this case, it is when a file that has Azure module references is opened the assemblies get loaded but not the actual modules.

PowerShell Version

> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.2.13
PSEdition                      Core
GitCommitId                    7.2.13
OS                             Darwin 21.6.0 Darwin Kernel Version 21.6.0: Thu Jul  6 22:20:00 PDT 2023; root:xnu-8020.240.18.702.13~1/RELEASE_A…
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visual Studio Code Version

> code-insiders --version 
1.82.0-insider
f1302be1e67e3af5fbeb8bbb2ea784de7bc96150
arm64

Extension Version

> code --list-extensions --show-versions | Select-String powershell

ms-vscode.powershell@2023.6.0

Steps to Reproduce

1. Close all PowerShell files
2. Restart session for PowerShell Extension
3. Run following command to list loaded assemblies

[System.AppDomain]::CurrentDomain.GetAssemblies() | Where-Object Location | Sort-Object -Property FullName | Select-Object -Property FullName, Location, GlobalAssemblyCache, IsFullyTrusted | Where FullName -like '*azure*' | ft

4. Note nothing is returned
5. Run Get-Module Az*
6. Nothing is returned
7. Open file (any file) with Az PowerShell references
8. Rerun step 3
9. All assemblies for the Az.Accounts and related commands are loaded
10. Rerun step 5
11. Nothing is returned
12. Run Import-Module Az.Accounts
13. Error returned: Import-Module: Assembly with same name is already loaded

Visuals

VSCode-PowerShell-Az.mp4

Logs

ext_logs.zip

[SydneyhSmith]

Thanks Shawn Melton (@wsmelton) , to clarify is this a new issue for you or has this been happening on previous versions of the extension?

"If you load a PowerShell file that has references to Azure PowerShell commands the assemblies are being loaded without loading the module fully." We think this is happening from a Get-Help call in tab completion

It looks like the error itself may be coming from our resolve handler or something similar

[wsmelton]

Always happening since I started using an Apple device (M1), switched to this month ago. I can't recall if Windows device gives me this issue...I can test that shortly.

Extension versions I tried v2023.6.0 back to v2023.3.3, issue exist in all of them.

[wsmelton]

So I cannot replicate this on Windows (Windows 10, VS Code Insiders, PowerShell 7.2, and v2023.9.1).

[andyleejordan]

Well, that's interesting. Usually it's the other way around (issue occurs on Windows but nowhere else).

[wsmelton]

I'll grab diagnostic logs for the windows device I used tomorrow and upload them.

[andyleejordan]

Shawn Melton (@wsmelton) could you share your PSSA settings file? We noticed:

2023-09-05 08:05:03.512 -05:00 [VRB] Using Script Analyzer settings path - '/Users/smelton/ldx/Agents/ScriptAnalyzerSettings.psd1'.

and believe there is a PSSA rule that can cause modules to be imported when analyzing the file.

[wsmelton]

There is no PSSA settings file in the referenced project

We have this in most of the project's settings.json file:
"powershell.scriptAnalysis.settingsPath": "./ScriptAnalyzerSettings.psd1"

[andyleejordan]

Your log said it loaded '/Users/smelton/ldx/Agents/ScriptAnalyzerSettings.psd1', is there anything in that file? Could be a bug that it found it but might be what's going on.

[andyleejordan]

Oh wait nevermind also in the log:

[INF] Unable to find PSSA settings file at '/Users/smelton/ldx/Agents/ScriptAnalyzerSettings.psd1'. Loading default rules.

And I misread that earlier.