PowerShell (Core), as of 7.3.4, does not come with a built-in HTML parser – and this may never change. You must rely on a third-party solution, such as the PowerHTML module that wraps the HTML Agility Pack. The object model works differently than the Internet Explorer-based one available in Windows PowerShell; it is similar to … Read more
The solution isn’t quite as straightforward as one would hope: # Sample custom function. function Get-Custom { Param ($A) “[$A]” } # Get the function’s definition *as a string* $funcDef = ${function:Get-Custom}.ToString() “Apple”, “Banana”, “Grape” | ForEach-Object -Parallel { # Define the function inside this thread… ${function:Get-Custom} = $using:funcDef # … and call it. Get-Custom … Read more
Here’s an overview of the PowerShell SDK-related NuGet packages:Adapted from here. Note: System.Management.Automation is not recommended for direct use. To create stand-alone applications that host the PowerShell runtime in order to call PowerShell commands in-process: Use Microsoft.PowerShell.5.ReferenceAssemblies for .NET Framework (Windows-only) applications using the legacy Windows PowerShell runtime. Use Microsoft.PowerShell.SDK for (potentially cross-platform) .NET Core … Read more
Gert Jan Kraaijeveld’s helpful answer offers a solution for cmdlets that truly are available only in Windows PowerShell (not also in PowerShell [Core] 6+). In this particular case, however, as Lee_Daily notes in a comment, you can use the Get-CimInstance cmdlet, which is available in PowerShell [Core] 6+ too: Get-CimInstance CIM_Product | Select-Object Name, PackageCache … Read more