Format-table error

I'm getting the following error when calling either Format-List or Format-Table

#(removed actual names)
[Reflection.Assembly]::LoadFrom("C:\mypath\MyAssembly.dll")
$s = [MyObject]::ICollection

$s | where {$_.DisplayName -like ("*" + args[0] + "*")} | format-table
DBID,DisplayName -auto

and this is the error I'm getting

out-lineoutput : Object of Type
"Microsoft.PowerShell.Commands.Internal.Format.FormatStartData" is not legal
or not in the correct sequence. This is likely caused by a user-specified
"format-table" command which is conflicting with the default formatting.

This only happens when I'm running this as a PS1 script (file.ps1), when I
run these commands from the command-line it works fine.

And it's just the format-table command, if I remove that I get what I
expect, a long list of objects.

try this :

[void] [Reflection.Assembly]::LoadFrom("C:\mypath\MyAssembly.dll")

Problem is that different formatters are used on the pipeline

if you want the output also format it explicit e.g. | format-list

Greetings /\/\o\/\/

"Patrick Escarcega" <PatrickEscarcega@discussions.microsoft.com> wrote in
message news:246FB9DE-94A5-4810-BA8E-F52501C2DD90@microsoft.com...
> I'm getting the following error when calling either Format-List or
> Format-Table
>
> #(removed actual names)
> [Reflection.Assembly]::LoadFrom("C:\mypath\MyAssembly.dll")
> $s = [MyObject]::ICollection
>
> $s | where {$_.DisplayName -like ("*" + args[0] + "*")} | format-table
> DBID,DisplayName -auto
>
> and this is the error I'm getting
>
> out-lineoutput : Object of Type
> "Microsoft.PowerShell.Commands.Internal.Format.FormatStartData" is not
> legal
> or not in the correct sequence. This is likely caused by a user-specified
> "format-table" command which is conflicting with the default formatting.
>
> This only happens when I'm running this as a PS1 script (file.ps1), when I
> run these commands from the command-line it works fine.
>
> And it's just the format-table command, if I remove that I get what I
> expect, a long list of objects.
>
>

another thread about it (I think there was a better one with more info,but
can not find it )
this "feature" got me lots of times, as I almost always test by just pasting
the code into the console,

best thing to avoid this is too do hardcode formatting on all output in
scripts


http://groups.google.nl/group/micros...2703b0b605f3f2

Greetings /\/\o\/\/

"/\/\o\/\/ [MVP]" <mow001@hotmail.NoSpam> wrote in message
news:B3123566-072A-4244-A262-8CBD2B617367@microsoft.com...
> try this :
>
> [void] [Reflection.Assembly]::LoadFrom("C:\mypath\MyAssembly.dll")
>
> Problem is that different formatters are used on the pipeline
>
> if you want the output also format it explicit e.g. | format-list
>
> Greetings /\/\o\/\/
>
> "Patrick Escarcega" <PatrickEscarcega@discussions.microsoft.com> wrote in
> message news:246FB9DE-94A5-4810-BA8E-F52501C2DD90@microsoft.com...
>> I'm getting the following error when calling either Format-List or
>> Format-Table
>>
>> #(removed actual names)
>> [Reflection.Assembly]::LoadFrom("C:\mypath\MyAssembly.dll")
>> $s = [MyObject]::ICollection
>>
>> $s | where {$_.DisplayName -like ("*" + args[0] + "*")} | format-table
>> DBID,DisplayName -auto
>>
>> and this is the error I'm getting
>>
>> out-lineoutput : Object of Type
>> "Microsoft.PowerShell.Commands.Internal.Format.FormatStartData" is not
>> legal
>> or not in the correct sequence. This is likely caused by a user-specified
>> "format-table" command which is conflicting with the default formatting.
>>
>> This only happens when I'm running this as a PS1 script (file.ps1), when
>> I
>> run these commands from the command-line it works fine.
>>
>> And it's just the format-table command, if I remove that I get what I
>> expect, a long list of objects.
>>
>>
>

Thanks so much, that worked great, just that little [void] and my script
worked.

It's an unusual error thanks for helping.

"/\/\o\/\/ [MVP]" wrote:

> try this :
>
> [void] [Reflection.Assembly]::LoadFrom("C:\mypath\MyAssembly.dll")
>
> Problem is that different formatters are used on the pipeline
>
> if you want the output also format it explicit e.g. | format-list
>
> Greetings /\/\o\/\/
>
> "Patrick Escarcega" <PatrickEscarcega@discussions.microsoft.com> wrote in
> message news:246FB9DE-94A5-4810-BA8E-F52501C2DD90@microsoft.com...
> > I'm getting the following error when calling either Format-List or
> > Format-Table
> >
> > #(removed actual names)
> > [Reflection.Assembly]::LoadFrom("C:\mypath\MyAssembly.dll")
> > $s = [MyObject]::ICollection
> >
> > $s | where {$_.DisplayName -like ("*" + args[0] + "*")} | format-table
> > DBID,DisplayName -auto
> >
> > and this is the error I'm getting
> >
> > out-lineoutput : Object of Type
> > "Microsoft.PowerShell.Commands.Internal.Format.FormatStartData" is not
> > legal
> > or not in the correct sequence. This is likely caused by a user-specified
> > "format-table" command which is conflicting with the default formatting.
> >
> > This only happens when I'm running this as a PS1 script (file.ps1), when I
> > run these commands from the command-line it works fine.
> >
> > And it's just the format-table command, if I remove that I get what I
> > expect, a long list of objects.
> >
> >
>