4 ms·
Before you knock on "writing code that clicks things" remember that on Windows clicking things is the primary if not solitary interface to most of the system. E
by jdbernard 12y ago
Before you knock on "writing code that clicks things" remember that on Windows clicking things is the primary if not solitary interface to most of the system. Even the administrative interfaces are secondary to the visual interface. A lot of programs don't offer an API available to outside processes.
The most important thing about any program is correctness: does it work and do what it is supposed to do. The only thing cringe-worthy about having to script GUI interactions is that fact that the operating system and environment requires it.
- detaro 12y agoFor the server versions, Windows finally leaves this path, making PowerShell (that admittedly also takes some getting used to) a first class configuration system. You even can do something in the GUI and then check in a log what PowerShell commands were executed under the hood.
- pjc50 12y agoFrom which version of Server? Where does the log go? I have a use for this.
- detaro 12y agoI think it's from 2012? Here is a link that describes it: http://www.learnmsexchange.com/windows-servers/windows-server-2012/593-what-is-windows-powershell-history-viewer-in-windows-server-2012 http://www.learnmsexchange.com/windows-servers/windows-serve...