v2.4.0 of #PowerShell module ClassExplorer is released! New commands Invoke-Member and Get-AssemblyLoadContext
github.com/SeeminglySci...
v2.4.0 of #PowerShell module ClassExplorer is released! New commands Invoke-Member and Get-AssemblyLoadContext
github.com/SeeminglySci...
Think he just meant he'd give me credit for embarrassing code. Jokes on him though, I'm perfectly capable of embarrassing myself ๐
An image showing two ways to create script blocks in PowerShell. One is defined with curly braces and the other is created from a string.
Do you know what bound and unbound script blocks are in PowerShell?
I did not know but they are sometimes talked about in GitHub issues or in the community.
If you are interested, check out my blog post from the past:
mdgrs.hashnode.dev/scriptblock-...
Use `Span<>`. Not in the cards though (outside of implicit conversion for method arguments)
I'm definitely not suggesting the proliferation of the style choice, but I would also strongly recommend against someone removing said aliases in their profile.
So I mention it only because it is much harder to completely write off when a decent chunk of folks do it regardless of what any one individual thinks. You can use github code search to gauge usage of each
path:*.ps1 /\|\s*where [{a-zA-Z\-]/
path:*.ps1 /\|\s*where-object [{a-zA-Z\-]/
While I personally agree, `where` and `foreach` specifically are not as unanimous in the community. There's a not insignificant group of folks who believe they should be treated more like keywords, and using the full command name is less readable.
(Again, not me, just saying it's not as clear cut)
ehhhh I don't know how much I endorse IDispatch, but IUnknown is neat
One of these days you will see the glory of vtables. When you do, you'll finally feel complete and know true serenity. Through vtables, all things are possible (or maybe just virtual dispatch)
The #PowerShell and #openSSH community call is this Thursday 9:30am PST! Add any topics you'd liked covered in this discussion github.com/PowerShell/P...
If your #PowerShell module loads dlls that are widely used by other modules, it's a good practice to implement ALC (Assembly Load Context) so that the right version of dlls are always loaded.
Here is how I learned about PowerShell ALC: