I’ve known using Windows.Forms with Powershell for some time, but never really dove into it until recently. One of the reasons for this is that I don’t like the idea of making tools that can’t be picked apart by others in my department. Another reason is that unless your form is just to make the script easier to use, its pointless to use Forms with Powershell because you can’t use Threads like you can in C#!
Though I suppose you could “Thread” things by making each part a separate process (and form) and only update on user interaction. In other words, make a master callback that whenever anything happens it updates the display. This would mean that some inter-process communication would have to happen, perhaps one or more files that contain the “state” of the application.
Something to explore this coming week.
