Comments on: Tip: Passing Parameters Revisited http://blog.usepowershell.com/2009/03/tip-passing-parameters-revisited/ The Shell Is Calling Tue, 10 Jan 2012 04:24:21 +0000 hourly 1 http://wordpress.org/?v=3.1.3 By: Steven Murawski http://blog.usepowershell.com/2009/03/tip-passing-parameters-revisited/comment-page-1/#comment-37 Steven Murawski Tue, 17 Mar 2009 11:14:49 +0000 http://blog.usepowershell.com/2009/03/tip-passing-parameters-revisited/#comment-37 Thanks for checking my work Aleksandar. When doing that I normally set my initial values to $null, but I left it as $env:computername, so it kept trying to pipe the computer name through the command until Powershell's recursion limit was hit. My bad. Thanks for checking my work Aleksandar. When doing that I normally set my initial values to $null, but I left it as $env:computername, so it kept trying to pipe the computer name through the command until Powershell’s recursion limit was hit. My bad.

]]> By: Aleksandar http://blog.usepowershell.com/2009/03/tip-passing-parameters-revisited/comment-page-1/#comment-36 Aleksandar Mon, 16 Mar 2009 21:40:50 +0000 http://blog.usepowershell.com/2009/03/tip-passing-parameters-revisited/#comment-36 When I run it in V1: PS>Check-Service server1 The script failed due to call depth overflow. The call depth reached 101 and the maximum is 100. Similar thing in V2: PS>Check-Service server1 The script failed due to call depth overflow. The call depth reached 1001 and the maximum is 1000. + CategoryInfo : InvalidOperation: (1001:Int32) [], ParentContainsErrorRecordException + FullyQualifiedErrorId : CallDepthOverflow I've found this looking for an error message - http://www.manning-sandbox.com/message.jspa?messageID=59410 When I run it in V1:
PS>Check-Service server1
The script failed due to call depth overflow. The call depth reached 101 and the maximum is 100.

Similar thing in V2:
PS>Check-Service server1
The script failed due to call depth overflow. The call depth reached 1001 and the maximum is 1000.
+ CategoryInfo : InvalidOperation: (1001:Int32) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : CallDepthOverflow

I’ve found this looking for an error message – http://www.manning-sandbox.com/message.jspa?messageID=59410

]]> By: Steven Murawski http://blog.usepowershell.com/2009/03/tip-passing-parameters-revisited/comment-page-1/#comment-35 Steven Murawski Mon, 16 Mar 2009 13:16:19 +0000 http://blog.usepowershell.com/2009/03/tip-passing-parameters-revisited/#comment-35 I can't think of any reason off hand. I'm looking at it as an order of operations, which do I want to occur first, processing pipeline input or processing parameters being passed in from the expression. Using the BEGIN block means I'm prioritizing the expression's parameters, while using the END block would prioritize the pipeline input. In most cases, you would be using the function one way or the other and this wouldn't come in to play. Nice point. Thanks! I can’t think of any reason off hand. I’m looking at it as an order of operations, which do I want to occur first, processing pipeline input or processing parameters being passed in from the expression.

Using the BEGIN block means I’m prioritizing the expression’s parameters, while using the END block would prioritize the pipeline input.

In most cases, you would be using the function one way or the other and this wouldn’t come in to play.

Nice point. Thanks!

]]> By: Doug http://blog.usepowershell.com/2009/03/tip-passing-parameters-revisited/comment-page-1/#comment-34 Doug Mon, 16 Mar 2009 12:59:38 +0000 http://blog.usepowershell.com/2009/03/tip-passing-parameters-revisited/#comment-34 Is there a preference in doing the '$server | Check-Service –Service $service' in an BEGIN block over the END block? Is there a preference in doing the ‘$server | Check-Service –Service $service’ in an BEGIN block over the END block?

]]>