Ask Slashdot: Moving From *nix To Windows Automation?

Posted by timothy on Friday May 6, 2011 @10:55AM from the setting-expectation-levels dept.

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?"

1 of 427 comments (clear)

Min score:

Reason:

Sort:

Re:Best practices are best practices by Anonymous Coward · 2011-05-06 12:06 · Score: 0, Flamebait

YOU ARE
YOU ARE
YOU ARE = YOU'RE
YOU ARE != YOUR
For fuck's sake, it's not that fucking hard. Not once, not twice, but EVERY SINGLE FUCKING TIME you got it wrong. That's beyond a typo, that's pure fucking ignorance and stupidity. Do you really not know the fucking difference? Why would anyone take your advice if you can't get such a simple thing right? Honestly, I'd prefer the hundreds of other retarded "Durr Windows is sucks lol hurr durr i wanna suck Linus' cock" posts than this fucking disgrace.