PSCX 1.1 issues

Just an FYI to all... There are a few issues with PSCX 1.1 that Keith is
aware of:

1. Errors on screen when one uses Visual Studio Express.

Source:
http://www.codeplex.com/PowerShellCX...orkItemId=8765

Fix: "For now, you might want to comment out the line the profile that dot
sources Environment.VisualStudio2005.ps1."

2. PSCX profile brings PowerShell Analyzer 1.0.1.11 to a crash on startup
(confirmed only on Windows XP).

Source:
http://www.codeplex.com/PowerShellCX...orkItemId=8762

Fix: Unknown, but a member of the PSCX team suggested trying to comment out
the unusual aliases like "cd...".

Marco

Regarding the PSA startup crash: Could it be that the new AD provider is
the cause for it? I had issues before when doing my own PSProvider
implementation. AFAIK there is PSDrive created in the PSCX profile
somewhere.

Thomy

Marco Shaw wrote:
> Just an FYI to all... There are a few issues with PSCX 1.1 that Keith is
> aware of:
>
> 1. Errors on screen when one uses Visual Studio Express.
>
> Source:
> http://www.codeplex.com/PowerShellCX...orkItemId=8765
>
> Fix: "For now, you might want to comment out the line the profile that dot
> sources Environment.VisualStudio2005.ps1."
>
> 2. PSCX profile brings PowerShell Analyzer 1.0.1.11 to a crash on startup
> (confirmed only on Windows XP).
>
> Source:
> http://www.codeplex.com/PowerShellCX...orkItemId=8762
>
> Fix: Unknown, but a member of the PSCX team suggested trying to comment out
> the unusual aliases like "cd...".
>
> Marco
>
>

Don't think the AD provider is the issue. I've got pscx 1.1 installed on a
number of machines & it works fine. I've not seen any problems but then I
don't use PowerShell Analyser either
--
Richard Siddaway
Please note that all scripts are supplied "as is" and with no warranty
Blog: http://richardsiddaway.spaces.live.com/
PowerShell User Group: http://www.get-psuguk.org.uk


"Thomy Kay" wrote:

> Regarding the PSA startup crash: Could it be that the new AD provider is
> the cause for it? I had issues before when doing my own PSProvider
> implementation. AFAIK there is PSDrive created in the PSCX profile
> somewhere.
>
> Thomy
>
> Marco Shaw wrote:
> > Just an FYI to all... There are a few issues with PSCX 1.1 that Keith is
> > aware of:
> >
> > 1. Errors on screen when one uses Visual Studio Express.
> >
> > Source:
> > http://www.codeplex.com/PowerShellCX...orkItemId=8765
> >
> > Fix: "For now, you might want to comment out the line the profile that dot
> > sources Environment.VisualStudio2005.ps1."
> >
> > 2. PSCX profile brings PowerShell Analyzer 1.0.1.11 to a crash on startup
> > (confirmed only on Windows XP).
> >
> > Source:
> > http://www.codeplex.com/PowerShellCX...orkItemId=8762
> >
> > Fix: Unknown, but a member of the PSCX team suggested trying to comment out
> > the unusual aliases like "cd...".
> >
> > Marco
> >
> >
>

yep, i try to grab the aliases and get the resolved command, but if
the resolvedc command is null. it blows up.. will update my beta for
sometime soonish

on x64 Vista I get
Add-PSSnapin : No Windows PowerShell Snap-ins are available for version 1.

Anyone else?

"Marco Shaw" <marcoDOTshaw_@_gmailDOTcom> wrote in message
news:eLt%23$ArYHHA.4940@TK2MSFTNGP05.phx.gbl...
> Just an FYI to all... There are a few issues with PSCX 1.1 that Keith is
> aware of:
>
> 1. Errors on screen when one uses Visual Studio Express.
>
> Source:
> http://www.codeplex.com/PowerShellCX...orkItemId=8765
>
> Fix: "For now, you might want to comment out the line the profile that dot
> sources Environment.VisualStudio2005.ps1."
>
> 2. PSCX profile brings PowerShell Analyzer 1.0.1.11 to a crash on startup
> (confirmed only on Windows XP).
>
> Source:
> http://www.codeplex.com/PowerShellCX...orkItemId=8762
>
> Fix: Unknown, but a member of the PSCX team suggested trying to comment
> out the unusual aliases like "cd...".
>
> Marco
>

"Brandon Shell" <tshell.mask@mk.gmail.com> wrote in message
news:%23CwvBRdZHHA.1400@TK2MSFTNGP06.phx.gbl...
> on x64 Vista I get
> Add-PSSnapin : No Windows PowerShell Snap-ins are available for version 1.

Related?
http://blogs.msdn.com/mstehle/archiv...l-snap-in.aspx

Then I guess the question is:
"Keith, Can you make me a 64bit version?" The 32bit Powershell seems buggy
on x64

--
Brandon Shell
---------------
Stop by my blog some time
Blog: http://www.bsonposh.com/
PSH Scripts Project: www.codeplex.com/psobject
--------------------------------------

"Marco Shaw" <marcoDOTshaw_@_gmailDOTcom> wrote in message
news:OHVcT2iZHHA.4940@TK2MSFTNGP05.phx.gbl...
>
> "Brandon Shell" <tshell.mask@mk.gmail.com> wrote in message
> news:%23CwvBRdZHHA.1400@TK2MSFTNGP06.phx.gbl...
>> on x64 Vista I get
>> Add-PSSnapin : No Windows PowerShell Snap-ins are available for version
>> 1.
>
> Related?
> http://blogs.msdn.com/mstehle/archiv...l-snap-in.aspx
>

"Brandon Shell" <tshell.mask@gmail.com> wrote in message
news:eoDvCBlZHHA.2320@TK2MSFTNGP03.phx.gbl...
> Then I guess the question is:
> "Keith, Can you make me a 64bit version?" The 32bit Powershell seems buggy
> on x64

Are you sure you are running the 64 bit version of PowerShell -
$env:SystemRoot\system32\windowspowershell\v1.0\powershell.exe? The KB
article indicates that you can get this error when installing a snapin for
32-bit PowerShell on an x64 system. I wonder if you can have both 32-bit
and 64-bit PowerShell installed on x64? I don't have a 64-bit system so I
can't test this out myself but one of the other PSCX devs has a 64 bit OS
and I thought he was able to successfully install PSCX 1.1 on it.

--
Keith

You do have both availible on x64. The snapin works on 32 (labled powershell
(x86)) but not 64.

So to clarify. I am running Vista x64. I install PSCX 1.1.
The snapin loads in powershell (x86) but not in normal x64 powershell.


"Keith Hill" <r_keith_hill@mailhot.nospamIdotcom> wrote in message
news:740DE63D-80DF-4999-8D32-E49429FC881C@microsoft.com...
> "Brandon Shell" <tshell.mask@gmail.com> wrote in message
> news:eoDvCBlZHHA.2320@TK2MSFTNGP03.phx.gbl...
>> Then I guess the question is:
>> "Keith, Can you make me a 64bit version?" The 32bit Powershell seems
>> buggy on x64
>
> Are you sure you are running the 64 bit version of PowerShell -
> $env:SystemRoot\system32\windowspowershell\v1.0\powershell.exe? The KB
> article indicates that you can get this error when installing a snapin for
> 32-bit PowerShell on an x64 system. I wonder if you can have both 32-bit
> and 64-bit PowerShell installed on x64? I don't have a 64-bit system so I
> can't test this out myself but one of the other PSCX devs has a 64 bit OS
> and I thought he was able to successfully install PSCX 1.1 on it.
>
> --
> Keith