v0.6.1 - Beta Testing

[anonhostpi]

Release Notes:

Adds the -SkipDependencies switch for easier manual dependency management

See the r/PowerShell series on embedding engines in PowerShell:

• PowerShell Shauntlet
• Turning PowerShell into a Python Engine

To test, install it with PowerShell and PackageManagement (OneGet)

Import-Module Import-Package
# Import-Module New-DispatchThread # - v0.2.1
Import-Module New-ThreadController # - v0.3.0

# --- Avalonia ---

Import-Package Avalonia.Desktop -Offline
# Import-Package Avalonia.Win32 -Offline]

# --- ThreadExtensions ---

Set-DispatcherFactory ([ThreadExtensions.Dispatcher])

$t1 = New-ThreadController
$t1.Invoke({ Write-Host "test - ThreadExtensions" }).
    Invoke({ Write-Host "done - ThreadExtensions" }, $true) | Out-Null

# --- WPF ---

Write-Host
Set-DispatcherFactory ([System.Windows.Threading.Dispatcher])

$t2 = New-ThreadController -Name "Tester"
$t2.Invoke({ Write-Host "test - WPF" }).
    Invoke({ Write-Host "done - WPF" }, $true) | Out-Null

# Now supports Async scriptblocks:

Async { Write-Host "test - async 1" } -Sync # automatically disposed runspace
Async { Write-Host "test - async 2" } -Thread $t1 -Sync # if you don't want to dispose the runspace, you can use an existing one
Async { Write-Host "test - async 3" } -Thread "Tester" # you can also specify the thread by its name
 
Write-Host
Write-Host (Get-Runtime)
Write-Host
Write-Host "Threads:"

$Threads = Get-Threads
$Threads

Links:

• PowerShellGallery:
  • https://www.powershellgallery.com/packages/Import-Package/0.6.1
  • https://www.powershellgallery.com/packages/New-ThreadController/0.3.1
• Github ChangeLog: https://github.com/pwsh-cs-tools/core/commits/v0.6.1-beta

---

This discussion was created from the release v0.6.1 - Beta.