Taking Control with PowerShell Logic

[@kmontoya87]

This series is just phenomenal - finding something like this on KZbin can be a hit or miss, let alone specific to this subject - I'm just so appreciative for - thank you so much. This is Udemy quality if not more.

[@lahirupriyankara2183]

best powershell course on youtube thank you!!!

[@AndyRofe]

As someone who has been exploring PowerShell indepth more recently, your videos have been super helpful and you explain concepts in such a good way. The real world practical examples are incredibly handy too. Thanks for the time and effort you have put into this video series!

[@BijouBakson]

I've searched for over a year for a proper tutorial on this. Especially for the course on your website. Thank you so much.

[@Techthoughts2]

Glad it was helpful!

[@mikepackman1516]

I agree with most on here, this is a quality series of videos. I've been in IT since the 90s (and used be a programmer until University put me off for life lolz), but I've never made the switch to Powershell (mainly as I'm a network guy), but since returning to the company I'm at now, I'm doing a lot more server stuff and they love core, so I've been picking it up piecemeal, I've had some time off this week so I thought I'd get into it (books are ok, but it's nice to sit back and watch on the tv). Not sure why I was so hesitant in the past, but thanks for the kickstarting my journey into doing more with Powershell.

[@pallabba]

best video on power shell logic on internet..Thank you for creating such an amazing content

[@derekdwerlkotte1840]

Thank you for putting this series together! Can I make a request for another video / series of pulling a stored procedures from SQL server and different ways to go through data pulled from stored procedure's?

[@justethom]

One of the best series on KZbin as of today! Thanks a lot :)

[@OFabianoSilva]

I can learn a lot from this series

[@Greenerkev1]

Love it! Learned a lot. Thanks😊

[@LOOregano]

This is a very powerful video that really simplifies more complex things to newer people. Thank you!

[@pashupatimishra9335]

Great playlist to learn powershell.

[@tiagobial4]

there are lots of videos about powershell on the internet however none of them explained so well as you did; people are concerned about the content and not about how the content is presented.

[@s.baskaravishnu22]

Many thanks

[@dalefirmin5118]

9:27 On the first pass of the loop, we got the number ZERO, not the number ONE. The corresponding color is black so it's hard to see.

[@leetkhan]

Very well put.

[@ShivaBhardwaj-no3yu]

Hello, Thanks for the great Tutorial. I have two questions: 1Q. When I am typing $item.PSIsContainer, why IDE is not giving me suggestions for PSIsContainer? I just typed it manually as per video? 2Q. In this line "$largeProcesses = @()". That's how we create empty object in Powershell? Thanks!

[@JasonJonesoriginal]

On your rainbow "for" loop example. Why did you do -le 15 instead of -eq 15? The number 1 is less than 15 so shouldn't the loop have stopped immediately?

[@Techthoughts2]

for ($i = 0; $i -le 15; $i++) { Write-Host $i -ForegroundColor $i } The second designation for $i here $i -le 15 is the criteria for the loop to continue. If you put $i -eq 15 the loop would not run at all. Because $i starts at equal to 0, and would not run because $i does not equal 15. We put $i -le 15 because we want the loop to continue to run as long as $i is below 15.

[@tonyto8384]

whats the point of adding [int] in front of the variables when youre setting them to a number already? is that like declaring the variable as a constant? like an integer always

[@Techthoughts2]

Great question. PowerShell is a dynamically, implicit typed language. This means variable type can be dynamically inferred based on what you load into it. $x = 100 # this will be an int $x = 'str' #this will be a string ^ note here that $x gets CONVERTED from an int to a string. but sometimes PowerShell gets this wrong, and/or you just want to be explicit. So, PowerShell supports strongly typing a variable. [int]$x = 100 # this will be an integer no matter what and can now only be an integer. Now, you can't load a string into it, it will fail.

[@tonyto8384]

@@Techthoughts2 thank for the clear explanation! your PowerShell playlist has helped me so much :)

[@Johannes00]

My first program after watching a bunch of your videos! It checks and counts odds & evens in a user supplied range. :) I prefix my user variables with x to easily clear them from memory later. Clear-Host $xOdd, $xEven = 0, 0 $xBottomRange = Read-Host -Prompt "Enter bottom range" $xTopRange = Read-Host -Prompt "Enter top range" [console]::Beep(1000, 200) Write-Host `n "-- Starting Evaluation --" Start-Sleep -Seconds 1 Write-Host `n "Value | Result" `n "--------------" $xBottomRange..$xTopRange | ForEach-Object { if ($_ % 2 -eq 0) { Write-Host ([string]$_).PadLeft(5, " ") " | even" $xEven += 1 } else { Write-Host ([string]$_).PadLeft(5, " ") " | odd" $xOdd += 1 } } Write-Host `n "There are $xOdd odd(s) and $xEven even(s) in the range of $xBottomRange - $xTopRange" [console]::Beep(500, 200) Write-Host `n "-- Process Complete --" `n Remove-Variable x* Start-Sleep -Seconds 1

[@ConSys2023]

Update-Help: Failed to update Help for the module(s) 'Dism, Get-NetView, Kds, NetQos, PcsvDevice, PKI, PSReadline, Whea, WindowsUpdate' with UI culture(s) {en-US} : One or more errors occurred. (Response status code does not indicate success: 404 (The specified blob does not exist.).). English-US help content is available and can be installed using: Update-Help -UICulture en-US. Perhaps you can help solve this error in powershell...

[@asjadullahsarosh9762]

Getting error with elseif - The 'term' is not recognised as the name of a cmdlet

[@Warmachine-tu5zo]

Thanks for the videos they are great. I have one issue I cannot figure out for the life of me right now.. I copied your example completely and I am getting elseif: the term 'elseif' is not recognized as the name of a cmdlet, function, etc.. $pth = 'C:\users' $evalpth = Test-path $Pth if ($evalpth -eq $true) { Write-Host "$pth VERIFIED" } elseif ($evalpth -eq $false) { Write-Host "$evalpth NOT VERIFIED" }

[@Techthoughts2]

When copying and pasting into a PowerShell terminal the bracket({}) placements matter. In the code above your brackets are on their own lines and this is not supported when pasting directly into the console window. Change it to: $pth = 'C:\users' $evalpth = Test-path $Pth if ($evalpth -eq $true) { Write-Host "$pth VERIFIED" } elseif ($evalpth -eq $false) { Write-Host "$evalpth NOT VERIFIED" } This is discussed in length here: github.com/PoshCode/PowerShellPracticeAndStyle/issues/81

[@isaacmaag1294]

Still a little confused on what value the i variable is?

[@Techthoughts2]

In a foreach loop $i is often used as a placeholder to construct the loop. it represents the loop control. if you wanted to do something 15 times starting at 1, you would set the following: for ($i = 1; $i -le 15; $i++) { Write-Host "Times I've run: $i" } try it out!

[@guai9632]

prev vids was useful even for a skilled programmer who wants to grok ps quickly. but in this one you explaining how to program. too deep diving into basic stuff

[@Techthoughts2]

The series aims to make viewers successful at using PowerShell. That includes experienced folks as well as brand new folks who have never programmed before. So, a few videos will cover some basic programming concepts. We'll have 1 more video like this - Video 7 - Input & Output - and then we'll start diving into some really fun stuff. I'd expect more experienced programmers to skip several videos when the series is complete. Stay tuned as more PowerShell goodness is on the way!