Yet another Try Catch question. Iterating through a ForEach loop

Question

Confused on error handling in a Powershell ForEach loop. I’m looping through a list of registry keys, attempting
 to open each one. If it succeeds, I do a bunch of stuff. If it fails, I want to skip to the next iteration.
If I was doing It in VBScript I’d do this:
For Each Thing In colThings
Open Thing
If Err.Number <> 0 Then
“oops”
Else
Do stuff
Do stuff
Do stuff
End If
Next
This is what I came up with in PowerShell. It seems to work, but just doesn’t seem powershell-ish. There must be a better way to use the catch output than just creating a $return variable and assigning it success or fail?
ForEach ($subKeyName in $subKeyNames)
try{$subKey = $baseKey.OpenSubKey("$subKeyName")}
catch{$return = "error" }
If($return -eq "error" )
“Oops”
Else
Do stuff
Do stuff
Do Stuff

Answer 1

 
I totally get what you're saying about formatting. I don't' have any habits yet, since I've only been working in Powershell since... well, what time is it now?
Unfortunately, It Has Been Decreed that we are no longer to use VBScript for any engineering solutions at work, so my 15 years experience in it now needs to be transitioned over asap. I don't have the luxury of crawling before I run. I'm trying not to be
frustrated, but it's like an English major waking up one day and being told "You must now speak French exclusively. Here's a book."
The Do Stuff example of my ForEach loop is about 50 lines of code involving matching values in subkeys of this registry key with another and collecting output. I tried wrapping the whole thing in a try section based on some examples, but it seemed odd, that's
why I'm asking. I'm used to tightly focused error handling at the point where an error may occur.
In this example I'm only interested in whether or not I can open the subkey (it exists, but I may not have permission). If I can't, there's no point in continuing with this iteration of the loop, I want to skip to the next one. So why include all the "Do
Stuff" in the the try section? From a readability viewpoint, it doesn't seem helpful.
Also, there may be more error handling deeper in the code. If I then put that in a try/catch, and then something else inside that, now I have nested try/catches mixed in with nested if/elses, all wrapped in a For loop.
Again, I can see how it works logically, but for readability not so much, and having all these braces 50 lines apart to match up is giving me eye strain :).
It sounds like David is agreeing with jrv, that putting the entire ForEach loop code into a try/catch is the conventional way to do it. I guess it makes as much sense as putting it all in an If-else-Endif, and I just need to adjust my paradigm.
But if not, my specific question was more along the lines of, is there a built in way to tell that the catch section has been executed, rather than me using it to populate an arbitrary variable and then read it? In VBScript, you execute something, and the
next line, you check the Err.number. I wasn't sure if you could do that with a try/catch.