SeeminglyScience

Very excited to announce that I have joined the #PowerShell team at @Microsoft! Looking forward to spending even more time on PowerShell 🎉

v2.4.0 of #PowerShell module ClassExplorer is released! New commands Invoke-Member and Get-AssemblyLoadContext github.com/SeeminglyScien…

@Steve_MSFT @Slav636 @Alan_Florance @BoreanJordan @nohwnd Oh yeah for sure. To be clear though, through some prompts from @nohwnd we discovered that the implementation for += currently allocates many many times more than it needs to. Really simple optimization for the common case of object[] specifically

@SeeminglyScienc @Slav636 @Alan_Florance @BoreanJordan @nohwnd That should be discussed by the Engine WG

I love the #PowerShell Discord, @nohwnd and @SeeminglyScienc had a question around += on arrays which gave me a better understanding of how that all works and why it's so slow. Resulted in a great issue being opened with some low hanging fruit github.com/PowerShell/Pow…

@Steve_MSFT @Slav636 @Alan_Florance @BoreanJordan @nohwnd I think they meant why not implement Jordan's fix. Significantly improves perf for += without changing behavior at all

@Slav636 @Alan_Florance @BoreanJordan @nohwnd @SeeminglyScienc We had a very long discussion about this during PSCore6. We considered different options but ultimately it was too big of a breaking change. If you use a List, += will work just fine. The problem is @() and variants create an array and used by many existing scripts

Performance talks on #powershell will tell you to avoid += on arrays, because it copies the array to a new one every single time. But the reality is much worse. 🧵1/17

Have something cool you've made with #PowerShell? Sign up to show it off at the #PowerShell/#OpenSSH Community Call on May 16th, github.com/orgs/PowerShel…

Don't forget that our monthly aka.ms/pscommunitycall is today at our normal time!

Just finalised what could be my largest contribution to #PowerShell .NET named arguments support github.com/PowerShell/Pow…. Big thanks to @SeeminglyScienc for all this help. This was a fun exercise in learning about the pwsh parser/ast, compiler, and binder all in one!

Because of the progression of his brain cancer, Sean had a minimal details. He's now had a friend significantly expand the details in the writeup of his family's story. I had no idea things had gotten this bad. 🙁 Please share for reach. Consider donating if you can.

#PowerShell 7.4 GA is out! Read more about it here: devblogs.microsoft.com/powershell/pow…. Thanks to the team and community for making this possible!

Automatically convert lengthy multi-parameter #PowerShell commands to use splatting mikefrobbins.com/2023/10/19/aut… <<-- New blog article

PSResourceGet is generally available! Thanks to everyone who contributed to this effort! devblogs.microsoft.com/powershell/psr…

PSResourceGet (aka PSGet3.0) is GA. The culmination of a years-long huge amount of implementation and compatibility testing. Congrats to @sydneysmithreal and the entire underlying team. devblogs.microsoft.com/powershell/psr…

@awakecoding @Steve_MSFT Fair enough, I don't have any input on that side of things. Just to fully clarify, I'm only describing why I don't personally think it makes sense for us to create the equivalent of vscode-powershell for VS. (I get that that was a very small part of what you're talking about)

@SeeminglyScienc @Steve_MSFT I'm double-checking facts before writing a blog post on how to do all the manual steps required to do local and remote debugging of PowerShell cmdlets in Visual Studio. I don't think it is the PowerShell's team job to improve this, but really the Visual Studio team

What is the best way to develop, run and debug PowerShell scripts in Visual Studio? It doesn't seem to be a supported project type unless you install third-party extensions (marketplace.visualstudio.com/items?itemName…). Yes, I know about VSCode, but I'm really asking about Visual Studio here

@awakecoding @Steve_MSFT You're not wrong, and I do think we should do better at assisting the "all of a sudden writing binary cmdlets" crowd. That said, I'm not sure that would be sufficient justification for the level of effort involved (and for inevitably dismantling a community project)

@SeeminglyScienc @Steve_MSFT There's one compelling business case to be made: for all those C# developers out there that barely know PowerShell and get asked to wrap .NET managed (and sometimes unmanaged!) code in PowerShell cmdlets, they're going to want to stick to Visual Studio.

@awakecoding @Steve_MSFT I know you're just asking, but in case there's an implied "why not?" at the end there, that's my opinion on it.

@awakecoding @Steve_MSFT Since there's an existing extension provided by the community, it doesn't make sense for us to put a worse version up just so there's something official. I'm sure we could find the budget to throw up a minimal implementation but not long-term support.

Would anyone have any clue why calling CreateProcess with CREATE_NEW_CONSOLE would fail with 5 (Access Denied). I've been unable to replicate it myself but I know for sure that on a Server 2016/2019 host through WinRM it will fail with this flag but the same args work without it.

@BoreanJordan @awakecoding @Steve_MSFT Yeah ConPTY is the only way afaik to capture everything *and* not cause behavioral changes. Depending on what features you need it's not exactly as easy as it sounds, definitely possible though

@awakecoding @Steve_MSFT @SeeminglyScienc PowerShell by default doesn't redirect exe output unless you try to capture it or redirect it so they write directly to the console. Hence why a ConPTY is really the only sane solution here.

How would you record ⏺️ and stream a #PowerShell interactive terminal? What are ways to capture the streams from a PowerShell terminal, and what kind of file format could it be exported to in order to allow replaying with proper timing information?

We will be having a LIVE PUBLIC BUG BASH July 27th 9am-10am pdt (Seattle time) for PSResourceGet...more info and a Teams join link to follow🐛 🥳 (there will be async instructions provided afterwards for those who aren't able to join live)

Just pushed a prerelease version of the #PowerShell #Pester @code extension. This adds support for Pester 5.5, fixes bugs with having a large amount of test files, and adds a lot more logging to see whats going on. Give it a try and file any issues! marketplace.visualstudio.com/items?itemName…