Votes from Connect: 4

Original Date Submitted: 3/28/2015 6:08:31 AM

Description:
Contact Information
Handle: JasonHorner
Site Name: PowerShell
Feedback ID: 1208677

Frequency: PowerShell
Regression: gci | out-null
void

$null = gci

run the above inside of measure-command the problem gets worse as the number of iteration increase

Problem Description:
It seems to me that:

gci | out-null

should be the preferred way of expressing: discard output in PowerShell

However when running timings against alternatives
some of the the other constructs are much faster:

void

$null = gci

I realize this is likely due to the pipeline overhead. Would it be possible to optimize or mitigate this even if just for single value results?

if we can't fix or mitigate the problem the docs should be updated with a warning not to use out-null in performance critical sections ie tight | large loops

Take a look here:

http://stackoverflow.com/questions/5260125/whats-the-better-cleaner-way-to-ignore-output-in-powershell

for some real world timings and other feedback (I also validated behavior in V4)

Product Studio item created by Connect Synchronizer due to creation of feedback ID 1208677 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1208677).

Repro Steps:
gci | out-null
void

$null = gci

run the above inside of measure-command the problem gets worse as the number of iteration increase

Expected Results:
I'd expect all approaches to have nominally the same overhead except perhaps in extreme edge cases.

Internal BugId: 14350

Votes from Connect: 6

Original Date Submitted: 3/4/2015 12:59:24 AM

Description:
Contact Information
Handle: June Blender
Site Name: PowerShell
Feedback ID: 1159049

Frequency: Always Happens
Regression: Yes, this happens in all previous versions

Problem Description:
Stop-Transcript returns a string that contains the path to the transcript file. (The string has grammatical errors, too.)

e.g. Transcript stopped, output file is C:\Users\JuneBlender\Documents\PowerShell_transcript.JUNEB-SRV01.yk0IWlkr.2015030311
4238.txt

To use the file in a subsequent command, you have to parse it cmd.exe-style. PowerShell can do better. Returning a file path would allow you to pipe the output to further commands.

e.g.
PC C:> Stop-Transcript
C:\Users\JuneBlender\Documents\PowerShell_transcript.JUNEB-Server01.yk0IWlkr.20150303114238.txt

Product Studio item created by Connect Synchronizer due to creation of feedback ID 1159049 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1159049).

Repro Steps:
Start-Transcript:
Transcript started, output file is C:\Users\JuneBlender\Documents\PowerShell_transcript.JUNEB-Server01.yk0IWlkr.20150303114238.txt
...

Start-Transcript:
Transcript started, output file is C:\Users\JuneBlender\Documents\PowerShell_transcript.JUNEB-Server01.yk0IWlkr.20150303114238.txt

Expected Results:
Start-Transcript:
C:\Users\JuneBlender\Documents\PowerShell_transcript.JUNEB-Server01.yk0IWlkr.20150303114238.txt
...

Stop-Transcript:
C:\Users\JuneBlender\Documents\PowerShell_transcript.JUNEB-Server01.yk0IWlkr.20150303114238.txt

Internal BugId: 14284

Votes from Connect: 7

Original Date Submitted: 10/15/2014 7:52:37 AM

Description:
Contact Information
Handle: Derp McDerp
Site Name: PowerShell
Feedback ID: 1001403

Frequency: Always Happens
Regression: Yes, this happens in all previous versions

Problem Description:
PowerShell should create an [encoding] type accelerator that accepts objects derived from [System.Text.Encoding] and also the following strings:

String
Unicode
BigEndianUnicode
UTF8
UTF7
UTF32
Ascii
Default
Oem

then all cmdlets which take -Encoding should be rewritten to use [encoding] instead.

The Add-Content, Get-Content, and Set-Content cmdlets should take a [fsencoding] type that does the above but accepts the "Byte" string.

Product Studio item created by Connect Synchronizer due to creation of feedback ID 1001403 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1001403).

Repro Steps:
Expected Results:

Internal BugId: 11046

Running Update-ModuleManifest on a psd1 saved on the network with a UNC path fails as the ScriptsToProcess, TypesToProcess and FormatsToProcess attributes are set incorrectly in the new manifest.

Example against the AzureRM.profile manifest:

Original AzureRm.Profile.psd1 contains

Format files (.ps1xml) to be loaded when importing this module

FormatsToProcess = @(

'.\Microsoft.Azure.Commands.Profile.format.ps1xml'

)

Running
Update-ModuleManifest -Path "\<some unc path>\AzureRm.Profile.psd1" -ModuleVersion 1.0.3

Gives error

Update-ModuleManifest : Cannot update the manifest file '\<some UNC path>\AzureRM.Profile.psd1' because the manifest is not
valid. Verify that the manifest file is valid, and then try again.'The member 'FormatsToProcess' in the module manifest is not valid: Cannot find path 'C:.ps1xml' because
it does not exist.. Verify that a valid value is specified for this field in the 'C:\Users\hbuckle\AppData\Local\Temp\1187382189\NewManifest.psd1' file.'

Examing the temporary NewManifest.psd1 shows

Format files (.ps1xml) to be loaded when importing this module

FormatsToProcess = '....&#39;

Votes from Connect: 9

Original Date Submitted: 7/16/2015 4:32:00 PM

Description:
Contact Information
Handle: happysysadm
Site Name: PowerShell
Feedback ID: 1551725

Problem Description:
Hi,

it would be nice to have a Reverse-String cmdlet. One that takes a string and reverse it. For example, "asdf" becomes "fdsa".

It could be aliased to rs (for reverse-string).

The reverse method for [array] is ok, but having a cmdlet and/or a [string] method. would be better.

Other well-known languages have routines for this:

For instance in Perl 6 you have the flip routine, which returns the string reversed character by character.
"Perl".flip; # lreP
"ABBA".flip; # ABBA

Ruby has a reverse method:
str = "asdf"
reversed = str.reverse

Thanks
Carlo

Product Studio item created by Connect Synchronizer due to creation of feedback ID 1551725 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1551725).

Repro Steps:

Internal BugId: 15651

Votes from Connect: 17

Original Date Submitted: 11/23/2010 4:09:27 PM

Description:
Contact Information
Handle: Aleksandar Nikolic
Site Name: PowerShell
Feedback ID: 623892

Frequency: Always Happens
Regression: No, this is new to the most recent version

Problem Description:
I would like to see Enable-PSRemoting support for ComputerName parameter to enable remoting on a remote machine.

If you are in a domain environment then the ComputerName parameter would not mean much because you could use GPO to enable PowerShell remoting wherever you like. However, in a workgroup environment it could be quite useful.

Product Studio item created by Connect Synchronizer due to creation of feedback ID 623892 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=623892).

Repro Steps:
Expected Results:

Internal BugId: 2755

When configuring IIS using Powershell, the cmdlets that read or write to configuration do not work when the application pool is 32-bit.

There is no way of specifying the "bitness" of the application therefore by default the configuration is written to the web.config file in the Framework64 folder which is ignored for 32-bit applications.

This is also the case for IIS manager when using "Configuration Editor". You can choose the location of "Root Web.Config <location path="my website"> however this ignores whether the application is 32 or 64 bit and always writes to the 64 bit location in the Framework64 folder.

On many cmdlets it is possible to specify the clr version however this does not help when the application is 32-bit.

Votes from Connect: 5

Original Date Submitted: 10/30/2014 6:04:29 AM

Description:
Contact Information
Handle: Peter M10
Site Name: PowerShell
Feedback ID: 1014939

Frequency: Always Happens
Regression: Yes, this happens in all previous versions

Problem Description:
I would like to access the pipeline object with Where-Object without curly brackets like so:

1..10 | Where-Object $_ % 2 -eq 1

to get only uneven numbers.

Product Studio item created by Connect Synchronizer due to creation of feedback ID 1014939 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1014939).

Repro Steps:
1..10 | Where-Object $_ % 2 -eq 1

Expected Results:
Gives an "Cannot validate argument on parameter 'Property'." error.

Internal BugId: 13075

Votes from Connect: 3

Original Date Submitted: 8/22/2014 2:01:53 AM

Description:
Contact Information
Handle: Aaron Jensen
Site Name: PowerShell
Feedback ID: 951925

Frequency: Always Happens
Regression: I do not know if this issue existed previously

Problem Description:
Write-Error isn't supposed to take both a message and an exception (see help Write-Error), but you can pass both without getting the "Parameter set cannot be resolved using the specified named parameters." error message.

Also, when you use Write-Error in a catch block, and use both parameters, the original exception bubbles up instead of what gets written with Write-Error.

Product Studio item created by Connect Synchronizer due to creation of feedback ID 951925 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=951925).

Repro Steps:

I expect this to fail with a "Parameter set cannot be resolved using the specified named parameters." error. Instead, I see an error written.

Write-Error -Message 'Blarg!' -Exception (New-Object 'Exception')


# If you do the above in a catch block, the Write-Error message never shows, instead the exception bubbles up.

# I'd like to get a 'Parameter set cannot be resolved using the specified named parameters.' error instead so I can fix my authoring error.

try

{

    throw 'Blarg!'

}

catch

{

    Write-Error -Message 'my custom message' -Exception $_.Exception

}

$Error[0] | fl -Force

$Error.Clear()

# This is the code I *should* have written, but PowerShell doesn't help me write it!

try

{

    throw 'Blarg!'

}

catch

{

    Write-Error -Message 'my custom message' 

}

$Error[0] | fl -Force

Expected Results:

Internal BugId: 8965

Votes from Connect: 20

Original Date Submitted: 2/27/2009 5:16:35 PM

Description:
Contact Information
Handle: Itanium2
Site Name: PowerShell
Feedback ID: 418906

Frequency: Always Happens
Regression: Yes, this happens in previous released versions

Problem Description:
For example, we have a folder and Administrator or Administrators group is object owner and doesn't have explicit (or inherited from parent) ACE with TakeOwnership right. Running code (see reprodiction steps) we get an error.

Product Studio item created by Connect Synchronizer due to creation of feedback ID 418906 (http://connect.microsoft.com/feedback/ViewFeedback.aspx?SiteID=99&FeedbackID=418906).

Repro Steps:
here is code that adds Everyone group to existing ACL:
$acl = Get-Acl C:\test
$accessRule = New-Object System.Security.AccessControl.FileSystemAccessRule("everyone", "FullControl", "Allow")
$acl.AddAccessRule($accessRule)
$acl | Set-Acl C:\test

while current user has TakeOwnership right - all works as expected. However if we remove this right for current user we get error:

Set-Acl : Attempted to perform an unauthorized operation.
At line:1 char:15
+ $acl | Set-Acl <<<< C:\test

+ CategoryInfo          : PermissionDenied: (C:\test:String) [Set-Acl], UnauthorizedAccessException

+ FullyQualifiedErrorId : System.UnauthorizedAccessException,Microsoft.PowerShell.Commands.SetAclCommand

Expected Results:
here is no neccessary to have TakeOwnership right if user is objects owner.

Internal BugId: 1949