Comments on: Conditional Logic Using Loops http://www.powershellpro.com Sharing the Experience Fri, 03 Feb 2012 08:09:32 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Praneeth http://www.powershellpro.com/powershell-tutorial-introduction/logic-using-loops/comment-page-1/#comment-740 Praneeth Fri, 25 Nov 2011 07:23:55 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/logic-using-loops/#comment-740 i want to validate remove command whether it is working or not for error handling how to do it pls tell me, i have tried if(Remove-MsolUser -userPrincipalName $args[1]) { success} else { failure} im getting failure for success & failure, why this is happening can u help me please......... Thanks & regards Praneeth i want to validate remove command whether it is working or not for error handling how to do it pls tell me, i have tried
if(Remove-MsolUser -userPrincipalName $args[1])
{
success}
else
{
failure}

im getting failure for success & failure, why this is happening can u help me please………

Thanks & regards
Praneeth

]]> By: George http://www.powershellpro.com/powershell-tutorial-introduction/logic-using-loops/comment-page-1/#comment-699 George Thu, 29 Sep 2011 18:08:54 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/logic-using-loops/#comment-699 I find that using the "continue" statement causes my script to terminate. Also, "Get-Command" and "Get-Command -CommandType All" do not retrieve a line for the command. Is my installation broken? I find that using the “continue” statement causes my script to terminate. Also, “Get-Command” and “Get-Command -CommandType All” do not retrieve a line for the command. Is my installation broken?

]]> By: Andy http://www.powershellpro.com/powershell-tutorial-introduction/logic-using-loops/comment-page-1/#comment-663 Andy Wed, 10 Aug 2011 18:48:36 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/logic-using-loops/#comment-663 Haji, Powershell also uses the familiar command shell from old (think DOS). It does this as a backwards compatibility for us legacy users. Therefore things like sifting through directories, delete/rename commands still work in the powershell console. Powershell will pass known commands such as these on to be executed as you would from say a run dialogue box or command prompt, assuming the executable is in the path environmental variables. Haji,

Powershell also uses the familiar command shell from old (think DOS). It does this as a backwards compatibility for us legacy users. Therefore things like sifting through directories, delete/rename commands still work in the powershell console. Powershell will pass known commands such as these on to be executed as you would from say a run dialogue box or command prompt, assuming the executable is in the path environmental variables.

]]> By: Haji Akhundov http://www.powershellpro.com/powershell-tutorial-introduction/logic-using-loops/comment-page-1/#comment-654 Haji Akhundov Thu, 21 Jul 2011 13:57:46 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/logic-using-loops/#comment-654 Dear Author, I just started learning PowerShell recently. your tutorial is great! Its a very good start for beginners! Thank you! p.s. in one of the examples above you launch a notepad by just typing notepad, same can be done by typing calc. But I really don't understand how this works on the background. Can any one explain how that works? regards =) Dear Author,
I just started learning PowerShell recently. your tutorial is great! Its a very good start for beginners! Thank you!

p.s.
in one of the examples above you launch a notepad by just typing notepad,
same can be done by typing calc. But I really don’t understand how this works on the background. Can any one explain how that works? regards =)

]]> By: Sam http://www.powershellpro.com/powershell-tutorial-introduction/logic-using-loops/comment-page-1/#comment-622 Sam Mon, 16 May 2011 07:15:20 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/logic-using-loops/#comment-622 Hey , what can I lunch a txt file on startup ? means when I start up my computer I want a txt file to open up. Hey , what can I lunch a txt file on startup ? means when I start up my computer I want a txt file to open up.

]]> By: Rueben http://www.powershellpro.com/powershell-tutorial-introduction/logic-using-loops/comment-page-1/#comment-548 Rueben Tue, 14 Dec 2010 18:35:43 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/logic-using-loops/#comment-548 Hi Cathy, The error resides in the second line of the code: $colItems = get-wmiobject -class “Win32_Processor” -namespace “root\CIMV2? ` The last quotation mark is different than all the rest, simply replace it via the PowerShell ISE to get the right one and terminate the string correctly, so that the rest of the strings can be properly initiated and terminated. Hi Cathy,

The error resides in the second line of the code:

$colItems = get-wmiobject -class “Win32_Processor” -namespace “root\CIMV2? `

The last quotation mark is different than all the rest, simply replace it via the PowerShell ISE to get the right one and terminate the string correctly, so that the rest of the strings can be properly initiated and terminated.

]]> By: Cathy http://www.powershellpro.com/powershell-tutorial-introduction/logic-using-loops/comment-page-1/#comment-531 Cathy Wed, 10 Nov 2010 16:43:51 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/logic-using-loops/#comment-531 I have copied and pasted the code for Processor Info but when I run it I am getting: The string starting: At C:\!WORK\Powershell\ProcessorInfo.ps1:13 char:19 + write-host "Name: <<<< "$objItem.Name is missing the terminator: ". At C:\!WORK\Powershell\ProcessorInfo.ps1:15 char:2 + } <<<< +CategoryInfo : ParserError: ( $objItem.Name write-host }:String) [], ParseException +FullyQualifiedErrorID: TerminatorExpectedAtEndOfString So I am a little lost? I have copied and pasted the code for Processor Info but when I run it I am getting:

The string starting:
At C:\!WORK\Powershell\ProcessorInfo.ps1:13 char:19 + write-host “Name: <<<< "$objItem.Name is missing the terminator: ".
At C:\!WORK\Powershell\ProcessorInfo.ps1:15 char:2 + } <<<<
+CategoryInfo : ParserError: ( $objItem.Name write-host }:String) [], ParseException +FullyQualifiedErrorID: TerminatorExpectedAtEndOfString

So I am a little lost?

]]> By: Dr.kipp http://www.powershellpro.com/powershell-tutorial-introduction/logic-using-loops/comment-page-1/#comment-466 Dr.kipp Wed, 07 Apr 2010 09:02:50 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/logic-using-loops/#comment-466 how do i make loops count with two figures (01 and to 80 for instance) how do i make loops count with two figures (01 and to 80 for instance)

]]> By: Quentin http://www.powershellpro.com/powershell-tutorial-introduction/logic-using-loops/comment-page-1/#comment-373 Quentin Wed, 15 Jul 2009 22:20:47 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/logic-using-loops/#comment-373 T Pops is right - changing True to False does nothing, because Responding is a boolean, and it seems "string" -eq boolean is always true. Better option may be foreach ($item in Get-Process) { if ($Item.Responding) {write-host $Item.Name}} T Pops is right – changing True to False does nothing, because Responding is a boolean, and it seems “string” -eq boolean is always true.

Better option may be
foreach ($item in Get-Process) {
if ($Item.Responding) {write-host $Item.Name}}

]]> By: T Pops http://www.powershellpro.com/powershell-tutorial-introduction/logic-using-loops/comment-page-1/#comment-348 T Pops Fri, 05 Jun 2009 18:35:42 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/logic-using-loops/#comment-348 If you replace "True" with "False" in your example: foreach ($item in Get-Process) {if ($item.Responding -eq “True”){Write-Host $Item.Name}} It produces the same result. Am I missing something or is a bad script or what? If you replace “True” with “False” in your example:

foreach ($item in Get-Process)
{if ($item.Responding -eq “True”){Write-Host $Item.Name}}

It produces the same result. Am I missing something or is a bad script or what?

]]>