Working with PowerShell background jobs

[@nazerbor3i]

There is something called Tab completion

[@ddaltonyvcc]

I know. It is something I personally don't use very often but I know a log of people who don't like typing who do. For those of you who are not familiar with it, you can start typing the command and then hit the tab key. If you have typed enough of the command for PowerShell to determine what command you want, PowerShell will complete the command for you. If you have not, PowerShell will cycle through the options based on what you have typed up to that point. If you are not a great typist, it is a very convenient feature.

[@000djw000]

PowerShell Jobs are from many years ago! People do not write scripts that use jobs now.

[@natestrings673]

What is appropriate to use now instead?

[@goonbreathfpv]

@@natestrings673 runspaces

[@natestrings673]

@@goonbreathfpv You really unlocked a big door in my dev journey with this. Thank you so much for this simple, yet extremely useful information!

[@natestrings673]

@@goonbreathfpv What are best practices to avoiding deprecated methods of doing something in PowerShell? There's so much information that might have 3 or 4 new and better ways of doing something, but it's not always easy to find...