To avoid that problem, you'll want to set -o noclobber in scripts or, better, for your login shell, and let it be inherited by subshells, including those that run your shell scripts.

The Test-Path cmdlet can keep you from going bonkers by offering a little bit of script pre-error-handling.

1) Handling errors in PowerShell scripts: Utilize Try-Catch-Finally blocks as error handling mechanisms to manage exceptions without terminating the script prematurely.

Anyhow, I was writing a script and given that CTP3 now supports the good old try and catch error handling methodology. My error handling logic, of course, was using it.

To avoid errors, it's important to write PowerShell scripts that prevent code from running on an unintended platform. Luckily, this is easier to do than it sounds.

An easy way to protect shell scripts from creating havoc when they go wrong due to a missing directory is to replace the shell's cd command by a function declared at the start of the script: ...at the ...