I have Problems with the new PowerShell V2

=?Utf-8?B?Qmlzd2FuZ2VyRw==?=

Hello,
my Question for the new PowerShell.... i have installet the old Version with
PowerShellCX_1.1.1.

I have deinstalled the PowerShell V1 and Install the Version 2.

i like PowerShellCX_1.1.1 in the new V2, he give me a error message with
"Add-PSSnapin : Windows PowerShell snap-in "Pscx" is loaded with the
following warnings: Error loading the extended typ
e data file:
Pscx, C:\Programme\PowerShell Community
Extensions\TypeData\FileSystem.ps1xml(19) : Error in type
"System.IO.FileInfo":
Member "BaseName" is already present.
At C:\Dokumente und Einstellungen\Bisw******\Eigene
Dateien\WindowsPowerShell\profile.ps1:105 char:14
+ Add-PSSnapin <<<< Pscx"

What can i do? an the next problem was with the profile folder... he dosn't
exists..?! is in the new version no profile.ps1????

thx for help..

Oisin Grehan

On Nov 19, 11:45 am, BiswangerG <Biswang...@discussions.microsoft.com>
wrote:
> Hello,
> my Question for the new PowerShell.... i have installet the old Version with
> PowerShellCX_1.1.1.
>
> I have deinstalled the PowerShell V1 and Install the Version 2.
>
> i like PowerShellCX_1.1.1 in the new V2, he give me a error message with
> "Add-PSSnapin : Windows PowerShell snap-in "Pscx" is loaded with the
> following warnings: Error loading the extended typ
> e data file:
> Pscx, C:\Programme\PowerShell Community
> Extensions\TypeData\FileSystem.ps1xml(19) : Error in type
> "System.IO.FileInfo":
> Member "BaseName" is already present.
> At C:\Dokumente und Einstellungen\Bisw******\Eigene
> Dateien\WindowsPowerShell\profile.ps1:105 char:14
> + Add-PSSnapin <<<< Pscx"
>
> What can i do? an the next problem was with the profile folder... he dosn't
> exists..?! is in the new version no profile.ps1????
>
> thx for help..

Mr Big-Boss of Pscx himself has the fix nicely documented here:

http://keithhill.spaces.live.com/blo...?wa=wsignin1.0

- Oisin "pscx minion" Grehan

Oisin Grehan

On Nov 19, 11:45 am, BiswangerG <Biswang...@discussions.microsoft.com>
wrote:
> Hello,
> my Question for the new PowerShell.... i have installet the old Version with
> PowerShellCX_1.1.1.
>
> I have deinstalled the PowerShell V1 and Install the Version 2.
>
> i like PowerShellCX_1.1.1 in the new V2, he give me a error message with
> "Add-PSSnapin : Windows PowerShell snap-in "Pscx" is loaded with the
> following warnings: Error loading the extended typ
> e data file:
> Pscx, C:\Programme\PowerShell Community
> Extensions\TypeData\FileSystem.ps1xml(19) : Error in type
> "System.IO.FileInfo":
> Member "BaseName" is already present.
> At C:\Dokumente und Einstellungen\Bisw******\Eigene
> Dateien\WindowsPowerShell\profile.ps1:105 char:14
> + Add-PSSnapin <<<< Pscx"
>
> What can i do? an the next problem was with the profile folder... he dosn't
> exists..?! is in the new version no profile.ps1????
>
> thx for help..

Mr Big-Boss of Pscx himself has the fix nicely documented here:

http://keithhill.spaces.live.com/blo...?wa=wsignin1.0

- Oisin "pscx minion" Grehan

=?Utf-8?B?Qmlzd2FuZ2VyRw==?=

THX, for the help...

and 1 question again, what is with the Profile in PowerShell V2...
is not installet from PowerShell V2 Installer in my "Personal
Files\windowspowershell\profile.ps1" is this other in the new version??

"Oisin Grehan" wrote:

> On Nov 19, 11:45 am, BiswangerG <Biswang...@discussions.microsoft.com>
> wrote:
> > Hello,
> > my Question for the new PowerShell.... i have installet the old Version with
> > PowerShellCX_1.1.1.
> >
> > I have deinstalled the PowerShell V1 and Install the Version 2.
> >
> > i like PowerShellCX_1.1.1 in the new V2, he give me a error message with
> > "Add-PSSnapin : Windows PowerShell snap-in "Pscx" is loaded with the
> > following warnings: Error loading the extended typ
> > e data file:
> > Pscx, C:\Programme\PowerShell Community
> > Extensions\TypeData\FileSystem.ps1xml(19) : Error in type
> > "System.IO.FileInfo":
> > Member "BaseName" is already present.
> > At C:\Dokumente und Einstellungen\Bisw******\Eigene
> > Dateien\WindowsPowerShell\profile.ps1:105 char:14
> > + Add-PSSnapin <<<< Pscx"
> >
> > What can i do? an the next problem was with the profile folder... he dosn't
> > exists..?! is in the new version no profile.ps1????
> >
> > thx for help..
>
> Mr Big-Boss of Pscx himself has the fix nicely documented here:
>
> http://keithhill.spaces.live.com/blo...?wa=wsignin1.0
>
> - Oisin "pscx minion" Grehan
>

=?Utf-8?B?UmljaFM=?=

If I rememeber correctly V1 didn't create the profile folder 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


"BiswangerG" wrote:

> THX, for the help...
>
> and 1 question again, what is with the Profile in PowerShell V2...
> is not installet from PowerShell V2 Installer in my "Personal
> Files\windowspowershell\profile.ps1" is this other in the new version??
>
> "Oisin Grehan" wrote:
>
> > On Nov 19, 11:45 am, BiswangerG <Biswang...@discussions.microsoft.com>
> > wrote:
> > > Hello,
> > > my Question for the new PowerShell.... i have installet the old Version with
> > > PowerShellCX_1.1.1.
> > >
> > > I have deinstalled the PowerShell V1 and Install the Version 2.
> > >
> > > i like PowerShellCX_1.1.1 in the new V2, he give me a error message with
> > > "Add-PSSnapin : Windows PowerShell snap-in "Pscx" is loaded with the
> > > following warnings: Error loading the extended typ
> > > e data file:
> > > Pscx, C:\Programme\PowerShell Community
> > > Extensions\TypeData\FileSystem.ps1xml(19) : Error in type
> > > "System.IO.FileInfo":
> > > Member "BaseName" is already present.
> > > At C:\Dokumente und Einstellungen\Bisw******\Eigene
> > > Dateien\WindowsPowerShell\profile.ps1:105 char:14
> > > + Add-PSSnapin <<<< Pscx"
> > >
> > > What can i do? an the next problem was with the profile folder... he dosn't
> > > exists..?! is in the new version no profile.ps1????
> > >
> > > thx for help..
> >
> > Mr Big-Boss of Pscx himself has the fix nicely documented here:
> >
> > http://keithhill.spaces.live.com/blo...?wa=wsignin1.0
> >
> > - Oisin "pscx minion" Grehan
> >

=?Utf-8?B?UmljaFM=?=

If I rememeber correctly V1 didn't create the profile folder 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


"BiswangerG" wrote:

> THX, for the help...
>
> and 1 question again, what is with the Profile in PowerShell V2...
> is not installet from PowerShell V2 Installer in my "Personal
> Files\windowspowershell\profile.ps1" is this other in the new version??
>
> "Oisin Grehan" wrote:
>
> > On Nov 19, 11:45 am, BiswangerG <Biswang...@discussions.microsoft.com>
> > wrote:
> > > Hello,
> > > my Question for the new PowerShell.... i have installet the old Version with
> > > PowerShellCX_1.1.1.
> > >
> > > I have deinstalled the PowerShell V1 and Install the Version 2.
> > >
> > > i like PowerShellCX_1.1.1 in the new V2, he give me a error message with
> > > "Add-PSSnapin : Windows PowerShell snap-in "Pscx" is loaded with the
> > > following warnings: Error loading the extended typ
> > > e data file:
> > > Pscx, C:\Programme\PowerShell Community
> > > Extensions\TypeData\FileSystem.ps1xml(19) : Error in type
> > > "System.IO.FileInfo":
> > > Member "BaseName" is already present.
> > > At C:\Dokumente und Einstellungen\Bisw******\Eigene
> > > Dateien\WindowsPowerShell\profile.ps1:105 char:14
> > > + Add-PSSnapin <<<< Pscx"
> > >
> > > What can i do? an the next problem was with the profile folder... he dosn't
> > > exists..?! is in the new version no profile.ps1????
> > >
> > > thx for help..
> >
> > Mr Big-Boss of Pscx himself has the fix nicely documented here:
> >
> > http://keithhill.spaces.live.com/blo...?wa=wsignin1.0
> >
> > - Oisin "pscx minion" Grehan
> >

Keith Hill [MVP]

"RichS" <RichS@discussions.microsoft.com> wrote in message
news:F47DD87F-E449-4881-B1FC-34F7BDA7E400@microsoft.com...
> If I rememeber correctly V1 didn't create the profile folder either

That's correct.

--
Keith