Ship built-in profiles in a well-known module path

[joeyaiello]

We'd like to ship a couple profiles (e.g. Style, Minimal, Full) in a well-known path (e.g. $PSModulePath\PSScriptAnalzyer\Profiles\Minimal.PssaProfile.psd1). That way we have built-in examples, and we can also modify -Profile to pick up profiles form that location (e.g. Invoke-ScriptAnalyzer foo.ps1 -Profile Minimal).

[raghushantha]

Create Profiles based on the best practices category from here:

https://github.com/PowerShell/PSScriptAnalyzer/blob/development/PowerShellBestPractices.md

Cmdlet Design Rules
Script Functions
Scripting Style
Script Security
DSC Related Rules

[KirkMunro]

Is it too late to use something other than Profile for this? I'd much
prefer Configuration, since it would be inline with remoting
(*-SessionConfiguration) and Profile has a different meaning in PowerShell
already.

*Kirk Munro *
Poshoholic, Microsoft MVP
Blog http://poshoholic.com/ | Twitter http://twitter.com/poshoholic |
LinkedIn http://ca.linkedin.com/in/kirkmunro | GitHub
http://github.com/KirkMunro | Facebook
http://www.facebook.com/#%21/kirk.munro

Need a PowerShell SME for a project at work? Contact me
http://poshoholic.com/contact-me/!

On Mon, Nov 23, 2015 at 2:19 PM, Raghu Shantha [MSFT] <
notifications@github.com> wrote:

Create Profiles based on the best practices category from here:

https://github.com/PowerShell/PSScriptAnalyzer/blob/development/PowerShellBestPractices.md

Cmdlet Design Rules
Script Functions
Scripting Style
Script Security
DSC Related Rules

—
Reply to this email directly or view it on GitHub
#354 (comment)
.

[juneb]

Kirk+1. I filed an issue about overloading this already very overloaded term: #350

BTW, I love the idea of canned profiles, but I wouldn't call them profiles.

[raghushantha]

#369