Ask Slashdot: Moving From *nix To Windows Automation?
Zubinix writes "I have a background in doing automation in a Unix/Linux environment using scripting languages such as perl and bash shell, as well as ssh for remote scripting. My next project will be in the Windows environment so what approach and methodology is best for developing, say, the automation required for a test system? I don't want to use things like Cygwin, as I need to integrate with Windows applications such as Exchange and Sharepoint. Is there a list of should and should not dos when it comes to Windows automation?"
Unless 100% of the applications that you need to integrate into your automation are driven by CLI or some kind of well-defined API, you'll be out of luck.
Windows isn't designed for automation. It's designed for moronic pointing and clicking.
Parity: What to do when the weekend comes.
Is there a list of should and should not dos when it comes to Windows automation?
Yes.
1. Do not do Windows automation.
That is all...
That is all.
Posted as me. 'Cause I care.
The soylentnews experiment has been a dismal failure.
Powershell is actually very powerful as it can extend or be extended by the .Net framework.
Excuse me while I shudder.
Have you got your LWN subscription yet?