I've just released a major update to PSCX that I hope folks will find
useful. You can download it from:

http://www.codeplex.com/PowerShellCX...tReleases.aspx

If you run into problems please report them here:

http://www.codeplex.com/PowerShellCX/WorkItem/List.aspx

The readme and about_pscx help topic are attached for you to check out what
is new in version 1.0. For me personally, I'm really liking the the
Get-CmdletMaml cmdlet which reflects over a snapin assembly and produces
PowerShell MAML help. It uses a number of attributes defined by PowerShell
and .NET as well as some defined by PSCX.



Enjoy!
--
The PSCX crew (Keith Hill, Alex Angelopoulos, Mabster, DBMsW, and MoW)

P.S. If you are passionate about PoSh and can contribute by writing C#
cmdlets, let me know. We're looking for more help.

Hi Keith,

> I've just released a major update to PSCX that I hope folks will find
> useful. You can download it from:

Very nice! Get-CmdletMaml - I like it ;-)

> P.S. If you are passionate about PoSh and can contribute by writing C#
> cmdlets, let me know. We're looking for more help.

Sounds interesting :-)

cu

Max

Great work Keith et all. There are some really useful things in this snapin
(e.g. awesome to run msbuild scripts via the PS console).

I have added the "Add-PSSnapin Pscx" line to my profile to load this and I
see it listed via Get-PsSnapin. But I can't seem to get the aliases (e.g.
galpscx) or functions (e.g. dirs) to work. Since I had my own profile I did
not choose the option to overwrite the profile during setup. What am I
missing here?

TIA
-Sourabh

"Maximilian Hänel" <ngSpam@smjh.de> wrote in message
news:%23BuZTYTHHHA.2632@TK2MSFTNGP06.phx.gbl...
> Hi Keith,
>
>> I've just released a major update to PSCX that I hope folks will find
>> useful. You can download it from:
>
> Very nice! Get-CmdletMaml - I like it ;-)
>
>> P.S. If you are passionate about PoSh and can contribute by writing C#
>> cmdlets, let me know. We're looking for more help.
>
> Sounds interesting :-)
>
> cu
>
> Max

There are a series of scripts that are included in PSCX.

Try to add this to your profile (assuming the scripts are in correct
location
_______________________________
.. "$env:PscxHome\Scripts\Debug.ps1"
.. "$env:PscxHome\Scripts\Prompt.ps1"
.. "$env:PscxHome\Scripts\PscxCmdletAliases.ps1"
.. "$env:PscxHome\Scripts\GenericAliases.ps1"
.. "$env:PscxHome\Scripts\GenericFilters.ps1"
.. "$env:PscxHome\Scripts\GenericFunctions.ps1"
.. "$env:PscxHome\Scripts\Cd.ps1"
.. "$env:PscxHome\Scripts\Dir.ps1"
.. "$env:PscxHome\Scripts\History.ps1"
.. "$env:PscxHome\Scripts\TabExpansion.ps1"
__________________________________

"Sourabh Mathur" <kksmkksm@yahoo.com> wrote in message
news:ea2G5elHHHA.3780@TK2MSFTNGP02.phx.gbl...
> Great work Keith et all. There are some really useful things in this
> snapin (e.g. awesome to run msbuild scripts via the PS console).
>
> I have added the "Add-PSSnapin Pscx" line to my profile to load this and I
> see it listed via Get-PsSnapin. But I can't seem to get the aliases (e.g.
> galpscx) or functions (e.g. dirs) to work. Since I had my own profile I
> did not choose the option to overwrite the profile during setup. What am I
> missing here?
>
> TIA
> -Sourabh
>
> "Maximilian Hänel" <ngSpam@smjh.de> wrote in message
> news:%23BuZTYTHHHA.2632@TK2MSFTNGP06.phx.gbl...
>> Hi Keith,
>>
>>> I've just released a major update to PSCX that I hope folks will find
>>> useful. You can download it from:
>>
>> Very nice! Get-CmdletMaml - I like it ;-)
>>
>>> P.S. If you are passionate about PoSh and can contribute by writing C#
>>> cmdlets, let me know. We're looking for more help.
>>
>> Sounds interesting :-)
>>
>> cu
>>
>> Max
>
>

"Brandon Shell" <tshell.mask@gmail.com> wrote in message
news:OAfSyKsHHHA.924@TK2MSFTNGP02.phx.gbl...
> There are a series of scripts that are included in PSCX.
>
> Try to add this to your profile (assuming the scripts are in correct
> location
> _______________________________
> . "$env:PscxHome\Scripts\Debug.ps1"
> . "$env:PscxHome\Scripts\Prompt.ps1"
> . "$env:PscxHome\Scripts\PscxCmdletAliases.ps1"
> . "$env:PscxHome\Scripts\GenericAliases.ps1"
> . "$env:PscxHome\Scripts\GenericFilters.ps1"
> . "$env:PscxHome\Scripts\GenericFunctions.ps1"
> . "$env:PscxHome\Scripts\Cd.ps1"
> . "$env:PscxHome\Scripts\Dir.ps1"
> . "$env:PscxHome\Scripts\History.ps1"
> . "$env:PscxHome\Scripts\TabExpansion.ps1"
> __________________________________

Brandon is correct. PSCX creates a system environment variable when it is
installed so that you can easily dot source whichever of the PSCX scripts
that you want. The PSCX cmdlet related aliases are all in
PscxCmdletAliases.ps1. The other scripts define aliases right with each
function/filter.

--
Keith