Vista - New-Object -ComObject x -Strict - A very good idea

I just noticed the -Strict SwitchParameter added to the ComObject parameter
set for New-Object. I like. It's nice to get a warning when PowerShell runs
into .NET wrapping behavior that might cause problems for scripters.

Yes, That is exactly the reason why we created the strict switch. We found
it hard to determine when we are getting COM object and .Net object. Often
times, script fails in a location Using this switch, you will get COM
object. if you get RCW class, new-object will fail. This makes it easy to
identify the issue earlier in the script than later.

--
Arul Kumaravel [MSFT]
Development Manager,
Windows PowerShell,
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights

"Alex K. Angelopoulos [MVP]" <a k a @ m v p s . o r g> wrote in message
news:OlQZqlNkGHA.1264@TK2MSFTNGP05.phx.gbl...
>I just noticed the -Strict SwitchParameter added to the ComObject parameter
>set for New-Object. I like. It's nice to get a warning when PowerShell runs
>into .NET wrapping behavior that might cause problems for scripters.
>
>