PowerShellPracticeAndStyle VS aws-tools-for-powershell

B. Performance related: https://github.com/PoshCode/PowerShellPracticeAndStyle/blob/master/Best-Practices/Performance.md

I'd also suggest taking a look at https://github.com/PoshCode/PowerShellPracticeAndStyle

There are likely other style guides to follow as well but I found this helpful when starting out: https://github.com/PoshCode/PowerShellPracticeAndStyle

Of course I can move the else up behind the curly brace... and although it is listed as a best practice in this best practice guide, I find it ugly and crowds the code. Regardless, it is syntactically correct everywhere else, so why is VS Code being a jerk?

I recommened reading the The PowerShell Best Practices and Style Guide.

PoshCode/PowerShellPracticeAndStyle: The Unofficial PowerShell Best Practices and Style Guide — https://github.com/PoshCode/PowerShellPracticeAndStyle

Is there any way in PowerShell to optimize the loading time of the module? for example, to edit the manifest file (AWSPowerShell.psd1), to load specific assemblies with the require cmdlets, in the module?

Maddeningly, the AWS Tools for Powershell doesn't support Get-Item natively: https://github.com/aws/aws-tools-for-powershell/issues/41

https://github.com/aws/aws-tools-for-powershell (although it's 95% C#)

One of these toolsets is targeted specifically towards PowerShell users and its name is AWS Tools for PowerShell. It is an open-source project and the source code is available on Github at https://github.com/aws/aws-tools-for-powershell/. It is available from PowerShell Gallery (https://www.powershellgallery.com) as an add-on modules to PowerShell, and it is available as a zip file download from AWS as well.