I've worked with several examples of both SharePoint Timer Jobs and PowerShell scripts, some of them doing the same things as the other. In my experience, PowerShell scripts are far more flexible, easy to test, and easy to deploy than SharePont Timer Jobs. The only advantage I can really think of to Timer Jobs is that they are written in C#.
What are the advantages/disadvantages of each? When is it better to use one or the other?
All comments that apply to 2010 and/or 2013 are weclome
answers i will not accept:
- you can schedule Timer jobs to run regularly - you can schedule powershell scripts as well, using the Task Scheduler
- Timer Jobs are all located centrally - you can simply agree to store all powershell scripts in a single folder