Keith Hill
Keith Hill
I'm sorry. I didn't realize this was a Rust-based utility. I see on the Rust repo this issue has come up - see: https://github.com/rust-lang/rust/issues/26258 https://github.com/rust-lang/rfcs/issues/1061 https://github.com/volks73/cargo-wix/issues/115 From this [documentation PR](https://github.com/volks73/cargo-wix/commit/bc06cb856f603a661050d9cc118bb71f973458bb)...
> However, on Windows, this could be a security concern as things like checking if a script is signed (and should be executed) only happens for .ps1 files. As a...
My preference is `~\.pwsh` (or `~\.powershell`) on Windows. The Microsoft guidance is to use `~\AppData\Local\Microsoft\PowerShell` or some folder like that under `~\AppData\Local`. My problem with that is `AppData` is hidden...
> If someone were to ... want it processed, ... the user should explicitly pipe it through some sort of "stringify" PowerShell command ^ Agreed. > apparently it is prohibited...
>Output accumulates; return does not do the same thing as other languages; fix it. `return` does behave as you expect it to within a `class` method. The way "output accumulates"...
> In Bash, return exits a function, period. Huh? Bash accumulates output just the same: ``` hillr@Keith-Dell8500:~$ function foo() { > echo "Hello" > ls ~ > date > return...
Well, PowerShell is based on .NET which is garbage collected, so it shouldn't suffer memory "leaks". That doesn't mean you can't have a memory hoard though. So you do have...
@jzabroski This was brought up in https://github.com/PowerShell/PowerShell-RFC/pull/92 You might want to chime in there.
Yay, another PSObject unwrap issue. Fixed with PR #90.
Cool. I'd like to write this one.