To determine if a job is complete you will need to check the status of the job.

The form controls do not allow themselves to be accessed from a different thread (i.e., the job).Ģ. If you need to update a form control or show progress, use the Receive-Job cmdlet to gather any necessary information from the job first and then update the control from the main script. Never access or modify form controls directly from within a job. There are two caveats you need to keep in mind when using jobs within a Form.ġ. Suppresses the command prompt until one or all jobs are complete. Gets the background jobs that were started in the current session.

Starts a background job on a local computer. Please refer to the MSDN PowerShell Jobs help page for more information. For your convenience we will list the cmdlets that are directly related to jobs. This article will not cover the ins and outs of jobs and it expects the user has some basic knowledge of the jobs mechanism in PowerShell. In this case it will free up the GUI and allow it to respond to user input. If you truly want to make your forms responsive, you will need to move these slow scripts into another thread and in the PowerShell world this means using jobs.įor those of you who aren’t familiar with PowerShell Jobs, they allow you to run scripts while freeing up the console to perform other tasks. Previously I discussed how to make your loops more responsive in this article, but not every long script comes in the form of a loop. When working with GUIs you may have noticed that the Form can freeze when running long scripts.

Sapiens powershell