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?"
Just don't. [/sarcasm]
"Be particularly skeptical when presented with evidence confirming what you already believe." -
that and banging your head on your keyboard until the world makes sense again.
This is my sig. There are many like it but this one is mine.
What I read:
I have a background doing things in a logical way, in a stable environment that actually works, but thanks to some incompetent beancounters who have traded the company cow for some buzzword-compliant magic beans, my next project will be building an igloo in the ninth circle of hell.
But for the sake of supporting 'Ask Slashdot':
DO:
DO NOT:
To understand recursion, you must first understand recursion.
kludge@elvis:101>uname -a
Linux elvis.goaway.com 2.6.16-1.2069_FC4smp #1 SMP Tue Mar 28 12:47:32 EST 2006 i686 i686 i386 GNU/Linux
kludge@elvis:102>uptime
18:07:02 up 647 days, 21:56, 18 users, load average: 8.53, 7.78, 7.76