PSCX - problem with succesful configure

Topics: Developer Forum, Project Management Forum, User Forum
May 5, 2009 at 12:43 PM

Hello,

I'm new PowerShell user. My system is Windows Seven RC (build 7100 :) ) in x86 edition. I installed PSCX in 1.1.1 version. I always run PowerShell as administrator rigths. I did set-executionpolicy remotesigned succesful, but I have still problem. I recive error:

Add-PSSnapin : Windows PowerShell snap-in "Pscx" is loaded with the following warnings:  The following error occurred w
hile loading the extended type data file:
Pscx, C:\Program Files\PowerShell Community Extensions\TypeData\FileSystem.ps1xml(19) : Error in type "System.IO.FileIn
fo": Member "BaseName" is already present.
At D:\Documents\WindowsPowerShell\profile.ps1:98 char:14
+     Add-PSSnapin <<<<  Pscx
    + CategoryInfo          : InvalidData: (Pscx:String) [Add-PSSnapin], PSSnapInException
    + FullyQualifiedErrorId : AddPSSnapInRead,Microsoft.PowerShell.Commands.AddPSSnapinCommand

Set-Alias : Alias is not writeable because alias measure is read-only or constant and cannot be written to.
At D:\Documents\WindowsPowerShell\profile.ps1:79 char:11
+     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 saps is read-only or constant and cannot be written to.
At D:\Documents\WindowsPowerShell\profile.ps1:79 char:11
+     Set-Alias <<<<  $name $value -Scope Global -Option AllScope -Force:$force -Description "PSCX $type alias"
    + CategoryInfo          : WriteError: (saps: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 D:\Documents\WindowsPowerShell\profile.ps1:79 char:11
+     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

Set-Alias : Alias is not writeable because alias gcs is read-only or constant and cannot be written to.
At C:\Program Files\PowerShell Community Extensions\Profile\Debug.ps1:72 char:10
+ set-alias <<<<  gcs Get-CallStack -Option AllScope -Description "PSCX function alias"
    + CategoryInfo          : WriteError: (gcs:String) [Set-Alias], SessionStateUnauthorizedAccessException
    + FullyQualifiedErrorId : AliasNotWritable,Microsoft.PowerShell.Commands.SetAliasCommand

Set-Alias : Alias is not writeable because alias ebp is read-only or constant and cannot be written to.
At C:\Program Files\PowerShell Community Extensions\Profile\Debug.ps1:89 char:10
+ set-alias <<<<  ebp Enable-Breakpoints -Option AllScope -Description "PSCX function alias"
    + CategoryInfo          : WriteError: (ebp:String) [Set-Alias], SessionStateUnauthorizedAccessException
    + FullyQualifiedErrorId : AliasNotWritable,Microsoft.PowerShell.Commands.SetAliasCommand

Set-Alias : Alias is not writeable because alias dbp is read-only or constant and cannot be written to.
At C:\Program Files\PowerShell Community Extensions\Profile\Debug.ps1:103 char:10
+ set-alias <<<<  dbp Disable-Breakpoints -Option AllScope -Description "PSCX function alias"
    + CategoryInfo          : WriteError: (dbp:String) [Set-Alias], SessionStateUnauthorizedAccessException
    + FullyQualifiedErrorId : AliasNotWritable,Microsoft.PowerShell.Commands.SetAliasCommand

Can someone help me? What should I do?

Best regards.
Developer
May 5, 2009 at 6:41 PM
Thanks for the 1-star rating mate. Really makes it all worthwhile.

Pscx 1.1.1 was built before Win7RC and PowerShell 2.0/7100 existed. I don't think it's fair to rate our product based on incompatibilities of a product that is not even released yet.

That said, please run the code that is on the Release page (it's for fixing CTP2/CTP3 issue, but will also fix one of the issues above for Windows 7 RC.). Also, open your profile in notepad:

ps> notepad $profile

...and comment out all of the lines that start with "new-alias" with a # character. The reason these cause an error is because the latest version of powershell defines some aliases that don't exist in v1.0 of powershell.

-Oisin

May 5, 2009 at 8:04 PM
Edited May 5, 2009 at 8:05 PM
Thanks for reply, I ran this code before I wrote topic. In 7 RC is PowerShell in 1.0. version. Of course I have still this problem.
Coordinator
May 5, 2009 at 8:11 PM
Actually in Win7 RC, PowerShell is V2.  Best thing is to sit tight for a couple of days.  We are real close to releasing PSCX 1.2 which supports PowerShell V2.
May 5, 2009 at 8:17 PM
OK, sorry, I check it, in fact he is in 2.0 version. Sorry. So I must wait to PSCX 1.2 version.:) Thanks for information.