Windows PowerShell Blog

Is there a URL or something for your preferred means of feedback?  I'd like to post where I know it will be read, but here is my comment:

The PS ISE is great, but I don't seem to see an option to print (and in color with line numbers).  Is this feature going to be available in the RTW? That along with the lack of intellisense is the only reasons I use other products, like PowerGUI, etc.  You guys are almost there...

I have trouble with this Command:

(Example from Tobias Weltners Book "Scripting mit Windows Powershell")

dir HKCU: -recurse -include *Powershell*

In Version 1.0 it goes.....

See Group:

http://groups.google.com/group/microsoft.public.windows.powershell/browse_thread/thread/54baffd8ef7d718a#

I would like to be able to create a new session in the PS ISE without closing and reopening the whole editor.  I was writing a WPF script last weekend and I was getting my session into a state where there was a variable or something that would not be reset between runs and when I would rerun the script it would generate errors and I had to completely close PS ISE and reopen the script to be able to run it again.  Something like the "clear output pane" that clears all my session variables and functions and such.

Also it would be nice if it could highlight the complementing open/close bracket/parenthesis when your cursor is next to one.

Also the example presented in about_functions_cmdletbindingattribute is misleading.  It needs to say:

function MyVerb-MyNoun {

 [CmdletBinding(SupportsShouldProcess ... etc)]

 Param()

 Begin{}

 Process{}

 End{}

}

Hi Jeffrey

Re: backwards compatibility, I have PoSh v2 CTP3 installed, and the PowerShell Community Extensions v1.1.1 installed.  These worked fine in CTP2, but now when I start PowerShell I get the following error:

Attempting to perform the InitializeDefaultDrives operation on the 'DirectoryServices' provider failed.

Set-Alias : Alias is not writeable because alias measure is read-only or constant and cannot be written to.

At C:\Program Files (x86)\PowerShell Community Extensions\Profile\Profile.ps1:79 char:14

+     Set-Alias <<<<  $name $value -Scope Global -Option AllScope -Force:$force -Description "PSCX $type alias"

   + CategoryInfo          : WriteError: (measure:String) [Set-Alias], SessionStateUnauthorizedAccessException

   + FullyQualifiedErrorId : AliasNotWritable,Microsoft.PowerShell.Commands.SetAliasCommand

Set-Alias : Alias is not writeable because alias start is read-only or constant and cannot be written to.

At C:\Program Files (x86)\PowerShell Community Extensions\Profile\Profile.ps1:79 char:14

+     Set-Alias <<<<  $name $value -Scope Global -Option AllScope -Force:$force -Description "PSCX $type alias"

   + CategoryInfo          : WriteError: (start:String) [Set-Alias], SessionStateUnauthorizedAccessException

   + FullyQualifiedErrorId : AliasNotWritable,Microsoft.PowerShell.Commands.SetAliasCommand

Is there something I've missed, maybe?

Alastair

Casting to a DateTime object doesn't respect the current culture of the thread. For example:

> [Threading.Thread]::CurrentThread.CurrentCulture

LCID  Name

----  ----

2057  en-GB

> [DateTime] "01/02/03"

02 January 2003

> # Note US date interpretation.

(alightly confusingly, there's also a CurrentUICulture property on the Thread object, but that always returns en-US, even though all my control panel settings are set to UK. When I try to set this to en-UK using Powershell, it has no effect.).

@Jeffrey

There are a few V1 cmdlets with issues or bugs. See Connect. I afraid some of them will not be fixed or improved, because you are officially in the end game of PowerShell V2, so that you are presumably concentrated now mostly on V2\V1 regressions and CTPs new bugs. At least it sounds and looks so. Well, it’s fair enough. But it won’t be fair if you say nothing in documentation and users, especially newcomers will waste their time instead of reading “this is not working, if ..., do this instead”.

Thanks,

Roman

I posted a list of notes for things I'd like to see in the ISE:

http://dougfinke.com/blog/index.php/2009/01/12/powershell-integrated-scripting-environment-increases-your-velocity-for-code-development/

* Can you please ISE be more extensible, for example it would be nice to allow scripts add WinForms controls on ISE tabs. Or create its own kind of tabs.

*can you please make ISE perform all interface function as in console powerShell.exe, history of command for example (with search)

*can you please made ISE embeddable in winforms applications

What is up on connect.microsoft.com?  It looks like someone went through all the old cases and closed most of them. Many were set to "Closed (Won't Fix)".  They also didn't have explanations as to why they won't be fixed.  Some appear to have been fixed, but were still set the same. These were all closed on or around 1/6/2009.  Since there are less than 300 closed cases for Powershell and about 147 of those were closed around 1/6/2009, either you were very, very, very busy or they were just closed to make room for V2.

I really hope this is a mistake and not just a way to get rid of cases.  Yes, many of them were old, some even from V1 RCX, but many were still valid bugs from after V1 was released.  It's a sad thing if they were just thrown away.  It does not encourage your users to give you new feedback if the old feedback was ignored.

Cool.  It looks like the cases being closed on connect.microsoft.com was an accident.  I just looked again and all the cases that were closed are open again.

Thanks

I encounter some behaviour I think is a bug:

$items = "item0", "item1", "item2"

$part = ($items | select-string "item0")

$items | where {$part -notcontains $_}

what do you think that $items be at the end of the script?

I was expecting "item1", "item2" but instead the value of $items is: "item0", "item1", "item2".

@Vladimir

I understand why it doesn't work (as a C# developer), but don't you think that the code SHOULD work (as a PowerShell user)?

The script look decent and the the whole purpose of PS was not to think about this sort of stuff (especially in the dynamic lang world).

It can be fixed by adding -asString to select-string (confusing) or by returning string objects from select-string or that "where" script will be able to deal with MatchInfo.

I would like to make two suggestions to the PowerShell ISE. First, allow drag-and-drog tab reordering. I find it very helpful to be able to group my open scripts. Second, have some method for copying the value of a variable to the clipboard when debugging. It is quite awkward typing in the variable and then select and copying the output from the Output Pane. Perhaps the way Visual Studio does it with its watch variable window could be a model.

would like to second previous comment about lack of print capability in ise editor window. for us ability to print scripts out is crucial -- admittedly can get this elsewhere (np++ for us), but would be a pain.

when using ls -r, it passes the basename to the pipe, rather than the full path. For some reason when you type ls -r -i *.* it will pass the full path to the pipe.