Keith Hill

@TylerLeonhardt True, but then PSSA will just turn around and tell you that you shouldn't be using aliases in scripts. 😉

Or maybe this for stable: ```powershell & {$OFS = ', '; @" PowerShell 7.2.0 Copyright (c) Microsoft Corporation. https://aka.ms/powershell $($exp = Get-ExperimentalFeature | Where-Object -not Enabled $exp ? "`nEnabled Experimental...

I wish GitHub had more reaction emojis. I'd like to 💯 @DHowett's comment above. :-)

WG-Engine discussed this today and decide to re-assign to the WG-Interactive-Console group.

OK, I'm taking a swag at importing the PSCX EditFileCommand.cs. Hopefully will have a PR soon-ish.

I'm fine with `Edit-Content`. The main thing we were trying to avoid is this approach: ``` Get-Content foo.csproj | % { $_ -replace $pattern,$replacement } | Set-Content foo.csproj ``` Where...

Hmm, the PSCX implementation has an elaborate way of supporting Path/LiteralPath that won't port over. @SteveL-MSFT is there a canonical sample of Path/LiteralPath C# code I can use?

@SteveL-MSFT Do you think this cmdlet should derive from `ContentCommandBase`? If not, I can't quite use that code as-is since it calls down into a base class to suppress wildcard...

@SteveL-MSFT Thanks. That got me past the Path/LiteralPath parameter issue. I have something that compiles and runs. However, I had to copy over some crufty PSCX code for the Encoding...

@SteveL-MSFT OK found some code in Out-File.cs but ... the Encoding parameter support required me to copy a number of `internal` classes. Sigh... In order to support "easier to write",...