Hello Keith Hill [MVP],
Point taken, but that being said, how does it stack up against traditional
runtime scripting languages in terms of performance and overhead?
Regards,
Pete Zerger, MCSE(Messaging) | MCTS(SQL 2005) | MCTS(Opsmgr) | MVP - Opsmgr
URL:
http://www.systemcenterforum.org
Training:
http://www.systemcenterforum.org/training
User Group:
http://www.systemcenterusergroup.com | Quote: |  | |
|
> "Pete Zerger" <pete.zerger@xxxxxx> wrote in message
> news:42cbe162b098ca6aa381eeb2f6@xxxxxx
> | Quote: | | | |
>> Hello Marco Shaw [MVP],
>>
>> You've touched on a topic I've been eager to discuss for some time,
>> so let me pose a question if I may.
>>
>> Presumably there are calls to the .NET framework when an instance of
>> Powershell is instantiated, correct? Would not this process of
>> starting Powershell when launching as a script as a scheduled task or
>> calling from a bat file before making WMI, ASDI or other calls result
>> in a longer time to completion?
>>
| | | | | > It's not just making some calls - PowerShell is entirely based on the
> .NET Framework. It's baked into the core.
>
> --
> Keith | |
| | |