
Now, there’s a bit of a Catch-22 in this process as Git looks for VS Code and VS Code looks for Git.

Next, download GIT for Windows ( there’s other versions). First, download VS Code but don’t install it right away. What I saw amazed me so much so that the time to learn became a non-starter. With a little downtime late last week, the opportunity presented itself to at least do a cursory search and skim of info on VS Code and PowerShell. There are several reasons why coding in any form are difficult for me, suffice it to say it took a few days to get over the, “Oh no, yet something else to learn” initial reaction to that prodding.


It turned out to be the auto-replaced hyphens that got introduced into that PowerShell step somewhere along the lines since I keep (kept) everything in OneNote. I had an error in a PowerShell step that puzzled me. It was Ben Thomas that gave me the prodding to look into Visual Studio Code (VS Code) for PowerShell coding and troubleshooting.
