Keith Hill

RE not a style canon - yeah I agree with that sentiment. Let's not go crazy with the Cheez Whiz here. Let's only offer style guidance (or recommend against a...

You know, the .NET Framework Design Guidelines book has many rule "annotations" from folks like Jeff Richter, Brad Abrams, Pattrick Dussud, etc. While the rules are usually pretty straight forward...

@Jaykul Yeah it needs a bit more nuance such as this should be done for the "main" parameter (however we define main parameter). And for the parameter type PSObject -...

Yeah I prefer lower case for built-in (accelerator) types e.g. `[string]`, `[switch]`, `[bool]`, etc. But when specifying a full .NET typename, I tend to use the .NET casing e.g. `[System.IO.Path]::Combine()`....

@KirkMunro It's been a while since I have looked at the accelerator list but yeah I see what you're saying and agree 100%.

Can you change the `"powershell.developer.editorServicesLogLevel"` setting to `Diagnostic` in your user settings and repro this again and attach that EditorServices.log file? That should provide a lot more detail during startup.

Doh! Not much of anything to go on there. Can you check the EventViewer on Windows. See if there is any error related to PowerShell in the Application log around...

PSSA has it's own settings file format. You can use it and configure user/workspace setting to point to that file: ``` "powershell.scriptAnalysis.settingsPath": "./PSScriptAnalyzerSettings.psd1", ``` The nice thing with this approach...

I used to use the Visual Studio test explorer and that was a real nice experience but that hasn't worked well in a long time (pretty much since we went...

I was under the impression that this would be hard (impossible?) to implement since PowerShell uses `dynamic` instead of `lexical` scoping. For instance, given this script: ``` $foo = "bar"...