Support for Powershell desktop as a user configuration or additional Kernel choice

When attempting to install and import the powershell module BcContainerHelper I get the following error during import stage

Install-Module BcContainerHelper -force Import-Module BCContainerHelper

Import-Module: Line | 2 | Import-Module BCContainerHelper | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | The script 'BcContainerHelper.psm1' cannot be run because it contained a "#requires" statement for PowerShell editions 'Desktop'. The edition of PowerShell that is required by the script does not match the currently running PowerShell Core edition.

I believe the issue is because .net interactive uses the cross platform powershell core edition and the module I’m attempting to use requires the desktop edition of powershell.

The same commands work successfully in Azure Data Studio which is using the Powershell Desktop Kernel

Adding support for Powershell Desktop edition either as a user configuration or as an additional Kernel choice would solve the problem.

[jonsequitur]

A separate PowerShell kernel that can be installed via a NuGet package might be the way to go here. We want to keep the number of pieces that are in the core relatively small, so functionality that won’t work cross-platform would be better as an extension.

[jonsequitur]

Installing new .NET Interactive subkernels via NuGet is supported today. You can see a very simple with our support for Mermaid and a more complex example with our support for T-SQL.

These aren’t standalone Jupyter kernels, though they become available via .NET Interactive’s Jupyter support. To include a pre-existing Jupyter kernel, this same mechanism could be used to create a proxy for it.