PowerShell Community Extensions

Source code checked in, #97987

r_keith_hill — Wed, 23 May 2012 05:04:37 GMT

Added ObsoleteAttribute to Ping-Host command.

Source code checked in, #97986

r_keith_hill — Wed, 23 May 2012 04:18:15 GMT

Fix Prompt module to put one space before the command in PowerShell_ISE. Also, remove the display of the path in the prompt for ISE since this theme displays the path in the ISE titlebar.

Source code checked in, #97985

r_keith_hill — Wed, 23 May 2012 04:07:32 GMT

Removed TabExpansion from PSCX v3. The tab expansion in built into PowerShell V3 is really pretty darn good.

Source code checked in, #97984

r_keith_hill — Wed, 23 May 2012 03:36:36 GMT

Finally got the PSModulePath stuff working!!!

Source code checked in, #97951

r_keith_hill — Tue, 22 May 2012 05:53:55 GMT

Removed commented out WiX xml.

Source code checked in, #97950

r_keith_hill — Tue, 22 May 2012 05:51:40 GMT

Installer is more or less functional at this point. Haven't added TabExpansion nested module yet.

Source code checked in, #97926

r_keith_hill — Mon, 21 May 2012 05:33:39 GMT

More work on WiX installer.

Source code checked in, #97924

r_keith_hill — Mon, 21 May 2012 04:34:21 GMT

More work on WiX installer.

Source code checked in, #97881

r_keith_hill — Fri, 18 May 2012 05:17:06 GMT

Work on help gen scripts and adding more to WiX installer.

Source code checked in, #97879

r_keith_hill — Fri, 18 May 2012 04:05:31 GMT

Added WiX 3.6 to Imports dir and added very basic (incomplete) PSCX MSI installer.

Source code checked in, #97771

r_keith_hill — Sun, 13 May 2012 05:01:47 GMT

Added gpar alias for Get-Parameter and move Get-PropertyValue function and alias to Deprecated module. Trivial replace in v3 is "... | % <prop-name>".

Created Issue: get-filetail does not work with files being used [32689]

cnmv_ti — Thu, 10 May 2012 14:41:17 GMT

Hello,

One of the most important uses for system administration of the get-filetail command is to monitor log files, like the Windows Update log file. But this does not work:

PS C:\Windows\System32> tail -wait -count 10 C:\Windows\System32\LogFiles\Firewa
ll\pfirewall.log
Get-FileTail : The process cannot access 'C:\Windows\System
32\LogFiles\Firewall\pfirewall.log' because it is being used by another process

Line: 1 Character: 5
+ tail <<<< -wait -count 10 C:\Windows\System32\LogFiles\Firewall\pfirewall.lo
g
+ CategoryInfo : NotSpecified: (:) [Get-FileTail], IOException
+ FullyQualifiedErrorId : System.IO.IOException,Pscx.Commands.IO.GetFileTa
ilCommand

(Note: actual messages in Spanish, translated by hand by me, for helping you).

In the source code of the file GetFileTailCommand.cs, we see:

var stream = new FileStream(filePath, FileMode.Open, FileAccess.Read, FileShare.ReadWrite)

The share mode is restricting access to files being concurrently written.

Commented Issue: RoboCopy Cmdlet [10128]

pamkkkkk — Thu, 10 May 2012 13:53:51 GMT

I think it would be valuble to have a RoboCopy cmdlet that mimics the functionality in RoboCopy. I have a few PowerShell scripts that need to do RoboCopy functions but i would prefer not to shell them out to RoboCopy.
Comments: ** Comment from web user: pamkkkkk **

PowerShell Robocopy is here:
http://robopowercopy.codeplex.com/
And best is: It supports long pathes up to 32000 characters Long

Closed Issue: Invoke-Ternary example doesn't work [30169]

r_keith_hill — Thu, 10 May 2012 03:49:40 GMT

The example given in the help for invoke-ternary does not work (for me, at least):

PS D:\> 1..10 | ?: {$_ -gt 5} {"Greater than 5";$_} {"Less than or equal to 5";$_}
Less than or equal to 5
Less than or equal to 5
Less than or equal to 5
Less than or equal to 5
Less than or equal to 5
Less than or equal to 5
Less than or equal to 5
Less than or equal to 5
Less than or equal to 5
Less than or equal to 5

This is Powershell 2.0 on Windows XP SP3.
Comments:

Source code checked in, #97717

r_keith_hill — Thu, 10 May 2012 03:37:16 GMT

Integrated Hal, Joel and Jason Archer's Get-Parameter into PSCX.

Source code checked in, #97559

r_keith_hill — Thu, 03 May 2012 04:12:01 GMT

Removed the SLS alias since PowerShell now defines it - as it should have all along. :-)

New Post: Pscx on Powershell 3.0 beta?

johnddx — Tue, 01 May 2012 08:05:42 GMT

I figured it out.

As I was upgrading, I temporarily moved the old pscx folder out of the Modules directory (into C:\Windows\System32\WindowsPowerShell\v1.0). Apparently, that is still in the search path for modules (presumably higher, too) because when import-module was run, it still wound up loading pscx.dll out of that sub-directory. renaming that directory from pscx to something else fixed the problem.

Interestingly, that may mean it's not technically necessary for modules to be placed in the modules folder. When I ran procmon, it looked like powershell might even have been searching the whole path.

New Post: Pscx on Powershell 3.0 beta?

johnddx — Tue, 01 May 2012 08:05:42 GMT

I figured it out.

New Post: Pscx on Powershell 3.0 beta?

johnddx — Tue, 01 May 2012 06:09:00 GMT

This is Windows 7, 32-bit.

I tried the "powershell.exe -ExecutionPolicy Unrestricted" command anyway, and it yields the same error. This is also after a reboot.

New Post: Pscx on Powershell 3.0 beta?

johnddx — Tue, 01 May 2012 06:09:00 GMT

This is Windows 7, 32-bit.

I tried the "powershell.exe -ExecutionPolicy Unrestricted" command anyway, and it yields the same error. This is also after a reboot.