Votes from Connect: 3

Original Date Submitted: 7/23/2015 12:20:40 AM

Description:
Contact Information
Handle: John.Bevan
Site Name: PowerShell
Feedback ID: 1578010

Frequency: PowerShell ISE
Regression: Run the below code / view the timings

$ip = '172.24.72.24' #amend for your environment

$hostname = [system.net.dns]::GetHostByAddress($ip).HostName


$begin=(get-date).ticks;test-connection $ip; $a=((get-date).ticks - $begin)

$begin=(get-date).ticks;test-connection $hostname; $b=((get-date).ticks - $begin)

$a-$b

#prove it's not caching; we can do this either way around

$begin=(get-date).ticks;test-connection $hostname; $b=((get-date).ticks - $begin)

$begin=(get-date).ticks;test-connection $ip; $a=((get-date).ticks - $begin)

$a-$b

#now let's see what measure-command says

(measure-command {test-connection $hostname}).ticks

(measure-command {test-connection $ip}).ticks

#that's not what we saw

NB: watching this you can see that the test-connection by IP is slow on each ping; not just on the first one.

Problem Description:
Running Test-Connection with an IP address, where the output is displayed performs significantly slower than Test-Connection does when passed a hostname (all else being equal).

However if output is not displayed (e.g. when using Measure-Command which hides the output from the pipeline, or when using the -Quiet parameter, Test-Connection is fractionally faster with an IP address than with HostName (as would be expected).

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

Repro Steps:
Run the below code / view the timings

$ip = '172.24.72.24' #amend for your environment

$hostname = [system.net.dns]::GetHostByAddress($ip).HostName


$begin=(get-date).ticks;test-connection $ip; $a=((get-date).ticks - $begin)

$begin=(get-date).ticks;test-connection $hostname; $b=((get-date).ticks - $begin)

$a-$b

#prove it's not caching; we can do this either way around

$begin=(get-date).ticks;test-connection $hostname; $b=((get-date).ticks - $begin)

$begin=(get-date).ticks;test-connection $ip; $a=((get-date).ticks - $begin)

$a-$b

#now let's see what measure-command says

(measure-command {test-connection $hostname}).ticks

(measure-command {test-connection $ip}).ticks

#that's not what we saw

NB: watching this you can see that the test-connection by IP is slow on each ping; not just on the first one.

Expected Results:
Test-Connection performance should be negligibly faster when given an IP than when given a DNS name (all else being the same).
Instead it's an order of magnitude slower (when output is passed back to the host).

Internal BugId: 15673

Votes from Connect: 10

Original Date Submitted: 5/19/2015 8:46:17 PM

Description:
Contact Information
Handle: azhskr
Site Name: PowerShell
Feedback ID: 1347198

Frequency: PowerShell ISE
Regression: Launch PowerShell ISE as either Administrator or non-Administrator
Get-Service BITS
Import-Module "Module Name"
Get-Module "Module Name"
Get-Service BITS
Remove-Module "Module Name"
Import-Module -Name "Module Name"
Get-Module -Name "Module Name"
Get-Module "Module Name"
Get-Service BITS

Problem Description:
Using Import-Module -Name "Module Name" imports the module, but breaks all output in the ISE. Using Import-Module "Module Name" imports the module and doesn't affect the output.

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

Repro Steps:
Launch PowerShell ISE as either Administrator or non-Administrator
Get-Service BITS
Import-Module "Module Name"
Get-Module "Module Name"
Get-Service BITS
Remove-Module "Module Name"
Import-Module -Name "Module Name"
Get-Module -Name "Module Name"
Get-Module "Module Name"
Get-Service BITS

Expected Results:
Using Import-Module with the name parameter should not break all output into the ISE console. The only way to fix it is to close and reopen the ISE.

Internal BugId: 14487

Votes from Connect: 10

Original Date Submitted: 1/18/2012 10:56:31 PM

Description:
Contact Information
Handle: HalR
Site Name: PowerShell
Feedback ID: 719121

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

Problem Description:
I would argue that in the ISE, the console should be treated co-equal to the script pane. If that's the case, why isn't there a New PowerShell Tab button just like there is a new script button? I would love to see a new toolbar icon to that effect.

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

Repro Steps:
Expected Results:
New toolbar icon for creating a PowerShell tab

Internal BugId: 3294