Stucco VS PowerShell

Used devblackops/Stucco: An opinionated Plaster template for high-quality PowerShell modules (github.com) to build the core module framework that has build capabilities and module dependencies built in, but still trying to understand the process from start to finish.

The stucco module offers a great starting place for building a module where the classes, private functions, and public functions are all kept in their own files and can be “compiled” into a single PSM1 at build time. I don’t think I’ve ever put everything in their own PSM1’s before. Instead, dot source the files you need in your root PSM1.

Like I did here : https://github.com/devblackops/Stucco/commit/21bce8c254e4578ec2bfebd29115af4f22d85348

I saw that the Stucco project has support for generating project files that can also generate Read The Docs sites but haven't tried it yet myself: devblackops/Stucco

You may also want to check out Stucco, which is my opinionated Plaster template for creating modules. It does most of the heavy lifting for you such as a decent Pester testing setup, psake tasks for local build/test automation, and your choice of CI. I'm also writing a book called Building PowerShell Modules on Leanpub which goes into all of this in detail.

msiexec.exe /package https://github.com/PowerShell/PowerShell/releases/download/v7.2.6/PowerShell-7.2.6-win-x64.msi /quiet ADD_EXPLORER_CONTEXT_MENU_OPENPOWERSHELL=1 ADD_FILE_CONTEXT_MENU_RUNPOWERSHELL=1 ENABLE_PSREMOTING=1 REGISTER_MANIFEST=1 USE_MU=1 ENABLE_MU=1 ADD_PATH=1

This smells like when PowerShell aliased curl and wget to a completely different command, with incompatible arguments.

https://github.com/PowerShell/PowerShell/pull/1901

PowerShell is available on macOS and Linux as well (source on Github: https://github.com/PowerShell/PowerShell). It may not be as well-integrated with things like system services management, but the language still works well. You can still use all the command line tools you're used to on Linux, of course.

nushell does look interesting, though the lack of a .deb repository does put it pretty low on my to-do list.

Issue #7940 discusses potential improvements to array slicing.

Note: This can be problematic as it prevents upstream commands from running their end {} block. See here. The new clean {} block introduced in PowerShell v7.3 does not suffer from this issue.

Can you give an example of something that PS can do that is built-in for text processing, instead of a proprietary symbolic query language?

[1] https://github.com/PowerShell/PowerShell

https://github.com/PowerShell/PowerShell/blob/master/LICENSE... is the MIT license. (Microsoft supplies debs directly which may reduce the motivation for Debian to do so.)

Oh, heh, also https://github.com/PowerShell/PowerShell/blob/master/docs/bu... the build script is written in PowerShell, so there's a bootstrapping problem :-) (Debian has solved those before of course, but with community sentiment like the above maybe noone is motivated to bother.)

According to https://github.com/PowerShell/PowerShell/issues/19628, the default behaviour is invoked whenever the completion script returns no output. To attempt to do so, I tried exiting the script via returning an empty string, or using the return keyword to exit the script completely, unfortunately with no avail. Is there a technique to achieve what I want, and is there any documentation about it other than the official one? Thank you in advance.