> $null $Template = ::GetTemplateContent( ::ToastText02) Here is how I did it (you can also grab the code in a Gist): Instead, I resorted to using native Windows 10 APIs, that would allow me to produce toast notifications, as if I am running a real application. The standard approach might have been using the console output, but that is just basic. I wanted to be alerted when they finish specific steps, error out, or are finished. Here is the thing about installation/system provisioning scripts - they can run for some time. And before someone says, “ But WSL - you can just re-use your Bash scripts!” Yes and no - I had some interesting dependencies that don’t quite translate as well to Bash, so here I am, stuck dealing with PowerShell. This led me down the rabbithole of trying to figure out how to use PowerShell to do things that I’ve been doing in Bash for the past couple of years. As part of this process, I started building some automation scripts - I’ve had that for macOS in the form of shell scripts that I could run whenever I re-installed the system, but nothing like that for Windows. That’s right, all those Mac machines, with the exception of one that I need for testing, have been Boot Camp-ed to use the latest and greatest of the Windows 10 ecosystem.
I recently moved all my development boxes to Windows.
Generating Windows 10 Notifications With PowerShell Learn how to produce native Windows 10 toast notifications from your PowerShell script.
0 kommentar(er)
