Scripting Operational Concerns

You can easily use command line scripting to automate tasks. You probably have already written my C# programs to do one-off processing or something that will run in production but on a separate server. It's my belief that pulling alot of code out of plugins is a good idea. It's easy to setup an Azure server to run your CLI programs.

Here's a link http://aappddeevv.github.io/dynamics-client to a general purpose CLI program (written in javascript/scala.js) that perform many different scripting tasks and is the basis for a library to write client specific processors, such as to create reminders, load data (very fast) using the standard dynamics data wizard but in an automated fashion, or upload webresources and solutions.

The idea is to create a robust library of often used components. You can use powershell for many things, and you should where it works well, but its not always an easy way to write robust utilities, in fact you would be better off writing python scripts, C# CLI programs or C# plugins for powershell in many cases.