Open o-l-a-v opened 3 weeks ago
Holy shit, yes please fix this. I've been tearing my hair out for months due to conflicts with 365 modules like Graph, Az Accounts (which is different to the Azure AD module that is being replaced by Graph), Exchange Online, Partner Center (even before it was officially deprecated)
The only fixes I've found are to either bash my head against the wall updating, uninstalling/reinstalling modules, trying random versions or killing and restarting the PowerShell extension in VScode. Or making separate scripts and running them in PowerShell 5 from the built in ISE, then saving the output and loading in another script in PowerShell 7 in vscode
Is your feature request related to a problem? Please describe the problem.
According to
vscode-powershell
maintainers, Azure PowerShell (and I assumeMicrosoft.Graph
too as I see similar problems with it) does not "implement assembly isolation correctly across the board".This can cause assembly conflict issues that
vscode-powershell
can't solve easily from their context.I don't have deep knowledge about this, I just want my authoring experience where Microsoft owns every part of the stack fixed.
Here are some resources on how, using assembly load context (ALC):
Here is more context:
Here are other related issues:
Describe the solution you'd like.
Find out if anything can be done here to make Microsoft.Graph modules play nice with
vscode-powershell
.Edit: Use AssemblyLoadContext for all assembly dependencies loaded by any Microsoft.Graph module.
Additional context?
No response