-
Powershell7(v 7.1.3) not detecting .Net Objects in VisualStudioCode(V1.55.0) Terminal
Getting "Object reference not set to an instance of an object.".
However, the script works fine in Powershell7…
-
## Description
I am getting a BadRequest error when trying to run Set-AzAutomationAccount to add customer managed keys to my automation account. When running with the -debug, I get the response b…
-
Windows is typically installed in C:\ however, the module should be more flexible to allow for windows being installed in other letters such as D:\
Suggest using a fact for this dynamic capability
-
Same as https://github.com/hashicorp/packer/issues/7049. This was never fixed, because unfortunately the issue was closed by the reporter.
His workaround was to remove the single quotes, and this w…
-
# Environment
```none
Windows build number: 10.0.19042.0
Windows Terminal version (if applicable): 1.5.10271.0
Any other software?
```
# Steps to reproduce
1. Click "Open Windows …
-
Powershell Image: `mcr.microsoft.com/azure-functions/powershell:3.0.15417-powershell7-appservice`
has the following:
```
root@a78c1b423bac:/# ls azure-functions-host/workers/powershell/7/runtim…
-
Currently if you use the Powershell provider it will use the powershell 5.x provider. we need to have the powershell 7 provider capability
-
- the powershell version is ：
$PSVersionTable
Name Value
PSVersion 7.1.3
PSEdition Core
GitCommitId 7.1.3
…
-
When trying to install the 7.1.2, the installer asks me for the path to the 7.1.0 msi installer to uninstall that version.
I had to download it but then the 7.1.2 installer fails saying it cannot …
-
I used the release from 25.09.2020 with an Windows 10 version 2004.
With Powershell 5.1 it does worked fine, but with Powershell 7.0 it got some errors.