Support large PowerShell projects
My dayjob revolves mostly around PowerShell. The largest PowerShell project I've worked on has over 50 000 lines of PowerShell code, the second largest has nearly 20 000. As you can imagine, supporting projects that large is simply impossible with PowerShell ISE. The company I work for bought licenses for PowerShell Studio from Sapien, which made working on the projects tolerable.
By far the biggest problem with the projects were exhaustingly numerous runtime errors. This was long before the era of PSScriptAnalyzer and Visual Studio Code.
Even with recent improvements to PowerShell tooling, I still feel like PowerShell is lacking in support of proper projects and prevention of runtime errors.
Now, you might argue projects this large should be moved to C#/F# and Visual Studio. However, PowerShell Studio costs a fraction of what Visual Studio Professional or Enterprise does. Visual Studio also lacks subscription model, buy license once, get updates and new versions as long as the license is valid. The current licensing model is very expensive, so outdated Visual Studio with MSDN license is all I get.
What I really would like to see:
- Official support for PowerShell projects all IDEs could support, introduce a new official file format to contain necessary project data.
- Optional support for variables being immutable by default.
- Support gradual typing. https://en.wikipedia.org/wiki/Gradual_typing
- Support compiling PowerShell script files and modules into dll file. Compilation would catch many runtime errors at compile time, while protecting scripts from accidental or intentional tampering.