PowerShell / WindowsCompatibility

Module that allows Windows PowerShell Modules to be used from PSCore6
Other
137 stars 33 forks source link

Powershell 7.0 bug #85

Open PhilMEFL opened 3 years ago

PhilMEFL commented 3 years ago

EXOCmdletTelemetry-20200806-112028.txt

Issue Type: Bug

Connect-ExchangeOnline -UserPrincipalName pma_adm@huleu.be -ShowProgress $true -EnableErrorReporting -LogDirectoryPath C:\temp\logs -LogLevel All generates always an error but is working with Posh 5.1

Extension version: 2020.6.0 VS Code version: Code 1.47.3 (91899dcef7b8110878ea59626991a18c8a6a1b3e, 2020-07-23T13:12:49.994Z) OS version: Windows_NT x64 10.0.19041

System Info |Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-3687U CPU @ 2.10GHz (4 x 2594)| |GPU Status|2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: unavailable_off
protected_video_decode: unavailable_off
rasterization: unavailable_off
skia_renderer: disabled_off_ok
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off_ok
webgl: enabled
webgl2: unavailable_off| |Load (avg)|undefined| |Memory (System)|7.87GB (1.00GB free)| |Process Argv|| |Screen Reader|no| |VM|0%|
corbob commented 3 years ago

Pretty sure this is not a vscode-powershell issue. According to the documentation the EXO V2 module isn't supported outside of windows PowerShell 5.1: Currently, the latest version of PowerShell that's supported for the EXO V2 module is PowerShell 5.1. Support for later versions of PowerShell (and by definition, support for Linux or Mac) is a work in progress.