#Project Guidelines
##Feature Design When designing features:
- All features must support both interactive and non-interactive consumption via PowerShell.
##Development
####1 General #####1.1 Follow MSDN Guidelines PowerShell usage must be consistent with, MSDN guidelines. (some useful links within those guidelines are: Module Installation, Command naming, Standard Cmdlet parameter Names and Types
####2 CI-Tasks #####2.1 Use string[] For Parameters Being Passed To Things Outside Powershell When defining a DevOps task, if a parameter will be used asa pass-through to something outside Powershell (example: invoking a .exe), make the parameter of type string[]. For a great background on why see powershell-call-operator-using-an-array-of-parameters-to-solve-all-your-quoting-problems