Rob Reynolds

Some of our validation stuff is a bit primitive in its checks through the powershell scripts. We should instead do this ``` c# Collection errors = null; var tokens =...

Requirement: Validate PowerShell

3

http://stackoverflow.com/a/10813842/18475 https://msdn.microsoft.com/en-us/library/system.management.automation.psparser(v=vs.85).aspx http://blogs.microsoft.co.il/scriptfanatic/2009/09/07/parsing-powershell-scripts/ While we shouldn't use this, it's important to note that it is there if we need it: POSH v3+ has AST support - https://msdn.microsoft.com/en-us/library/system.management.automation.language(v=vs.85).aspx

Requirement: No email address in any text related field

2

Following #96 - let's ensure email is not in any text related field like description, releaseNotes and/or tags.

Break out validation rules to their own dll

1

So that this can be used by things like choco

Add something for strictness - (loose, normal, strict)

1

This will allow strict for validating against things like dot org.

Following #122, create a nuget package

Relates to #9, using curl/wget to download should also be avoided.

https://github.com/PowerShell/PSScriptAnalyzer I found through https://github.com/PowerShell/PSScriptAnalyzer/issues/436 - we wouldn't necessarily use it for scoring, but for feedback to users on their scripts.