Would it be possible to get PowerShell into the Microsoft Store for Windows 10 in S Mode, in some sort of container that would allow for connections to exchange online powershell, and other tasks?

`
do you see that? that's the line continuation line in PS. very hard to notice because maybe you think it's a dirt on the screen or on a book.

would be better if lines continue until it meets a semi-colon. yes just like in C. a semi-colon is easier to notice and you wouldn't mistake it for a dirt on the screen.

cmdlets for Overriding Language not working in buid 1709/1803
Set-WinDefaultInputMethodOverride -InputTip ***-XXXXXX
Set-WinUILanguageOverride -Language XXXXXX

Does not change settings and generate no error message in PS

Many companies have several wifi ssids. You know, "Corp" "Guest" "Upstairs Lab"
Very very common.

How? How do you select one via PowerShell ?

Out-RsfolderContent fails when exporting Mobile Reports because the 'TypeName' MobileReport is not covered in the function.

I added the following remedy to my system. may be nice for others.
I have not yet tested for PowerBI reports ... but neither have the people making these nice modules ...

if (($item.TypeName -eq 'MobileReport') ) {
$relativePath = $item.Path
if($RsFolder -ne "/") { $relativePath = Clear-Substring -string $relativePath -substring $RsFolder -position front }
$relativePath = $relativePath.Replace("/", "\")
$newFolder = $Destination + $relativePath
Write-Verbose "Creating folder $newFolder"
New-Item $newFolder -ItemType Directory -Force | Out-Null
Write-Verbose "Folder: $newFolder was created successfully."
}

Hi,I have a loop like below. In that, I want to compare next iteration value with current iteration value. If current value is not match with next value then I need to do some process. So I want to know like how to get the next Iteration value of a loop in powershell.
$var = ('abc','abc','bcd','cdf','cdf')
Foreach($i in $var){ 
If($i -ne $nextiterationvalue) 
{       do something  } 
else  {     do something  }}

Thanks,Dinesh

our .net core projects use powershell. The lack of these commands impedes our cross-platform activities.

Setup group policy to enable PowerShell Transcripting. From a machine that has that policy applied, launch ADAC. The error "Cannot connect to any domain. Refresh or try again when connection is available." pops up and ADAC can't be used.

https://github.com/PowerShell/PowerShell/issues/3021

I am extremely annoyed by Test-NetConnection and would like to make it better. Why is there not a skip ICMP flag, or a timeout flag?

Please, OpenSource this so the community could improve this tooling for all.

Given a script with the contents:

```
$location = Get-Location

Write-Host "current directory [$($location.Path)]"
```

Actual:
From command prompt:
```
e:\projects\test>powershell -File ..\cleanBinObj.ps1
current directory [E:\projects]
```

From powershell:
```
E:\projects\test> ..\cleanBinObj.ps1
current directory [E:\projects\test]
```

Expected: calling powershell from the command prompt should preserve the current directory and print "E:\projects\test" instead of "E:\projects"

The cmdlet throws an exception that cannot be caught by scripts. It seems that the team that wrote the cmdlets was using the presence of -Online parameter to determine the parameter set, and pretended that -Online is always $true if is it supplied. It might not be -- it is perfectly valid to supply $false to the switch.

This should be considered a bug, as it crashes PowerShell. Presumably an ill-supplied set of parameters should result an ErrorRecord being written.

Dynamic param is silently ignored, and no errors are thrown when CmdletBinding is not defined.

[CmdletBinding()]
Param()

The following code should either run successfully, or throw an error:

Function Add-Control() {
DynamicParam {
$ParamAttribute = New-Object Parameter
$ParamAttribute.Mandatory = $true
$ParamAttribute.ParameterSetName = '__AllParameterSets'

$AttributeCollection = New-Object System.Collections.ObjectModel.Collection[System.Attribute]

$AttributeCollection.Add($ParamAttribute)

$controlTypes = @("TextBox", "Label", "DataGrid")

$AttributeCollection.Add((New-Object ValidateSet($controlTypes)))

$RuntimeParam = New-Object System.Management.Automation.RuntimeDefinedParameter('Type', [string], $AttributeCollection)

$RuntimeParamDictionary = New-Object System.Management.Automation.RuntimeDefinedParameterDictionary

$RuntimeParamDictionary.Add('Type', $RuntimeParam)

return $RuntimeParamDictionary
}

Process {
Write-Host ($PSBoundParameters['Type'])
}
}

Add-Control -Type "Test"
# $null

Note: This may ultimately require resolution in the .NET framework.

Recent versions of Windows 10 support mixed culture values such as `en-DE` (sic) (since version 1703 - see https://msdn.microsoft.com/en-us/library/cc233982.aspx)

After using, e.g., `Set-Culture en-DE` to set the culture for future PowerShell sessions (which in itself succeeds, as you can verify at registry location [HKEY_CURRENT_USER\Control Panel\International]), subsequent PowerShell sessions quietly fall back onto culture 'en-US', as reflected in $PSCulture and [cultureinfo]::CurrentCulture.

Note that such a mixed culture *is* honored in PowerShell *Core*.

Anaconda (Python Environments) Syntax Support