/\/\o\/\/ [MVP]

This is a problem with Write-only properties on COM objects and PowerShell.

I used MS scriptcontrol as a workaround for now, see for an example :

http://thepowershellguy.com/blogs/po...-services.aspx

Greetings /\/\o\/\/


"Karl Prosser[MVP]" wrote:

> I understand that. I was just thinking to see if its an STA issue or
> not, on a test box, to help isolate the problem.
> Colin Bowern wrote:
> > Hi Karl,
> >
> > I haven't tried v2 yet. With the product group saying that they will need a
> > year or so (give or take a quarter) I'm holding off including PSHv2 on our
> > production environment servers.
> >
> > Cheers,
> > Colin
> >
>

Colin Bowern

Not ideal, but I'll give it a shot. At least it keeps things compact.

Thanks!
Colin

"/\/\o\/\/ [MVP]" <oMVP@discussions.microsoft.com> wrote in message
newsBC13966-E781-4D21-8428-1EC5B9369874@microsoft.com...
> This is a problem with Write-only properties on COM objects and
> PowerShell.
>
> I used MS scriptcontrol as a workaround for now, see for an example :
>
> http://thepowershellguy.com/blogs/po...-services.aspx
>
> Greetings /\/\o\/\/
>
>
> "Karl Prosser[MVP]" wrote:
>
>> I understand that. I was just thinking to see if its an STA issue or
>> not, on a test box, to help isolate the problem.
>> Colin Bowern wrote:
>> > Hi Karl,
>> >
>> > I haven't tried v2 yet. With the product group saying that they will
>> > need a
>> > year or so (give or take a quarter) I'm holding off including PSHv2 on
>> > our
>> > production environment servers.
>> >
>> > Cheers,
>> > Colin
>> >
>>