You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 16, 2021. It is now read-only.
The best practices module, a standard module in WIndows can not be loaded by PowerShell 7 as it's not based (yet) on .NET Core. However, it also does not load with WIndows Compatibility module:
PS [C:\foo> ]>import-winmodule bestpractices
Import-Module : Failed to generate proxies for remote module 'BestPractices'. Running the Get-FormatData command in a remote session reported the following error: Unable to cast object of type 'Microsoft.PowerShell.Commands.Internal.Format.ControlReference' to type 'Microsoft.PowerShell.Commands.Internal.Format.ComplexControlBody'..
At C:\Program Files\PowerShell\Modules\WindowsCompatibility\1.0.0\WindowsCompatibility.psm1:531 char:13+Import-Module-Name $ImportNames-NoClobber:$NoClobber @ ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Import-Module], InvalidOperationException
+ FullyQualifiedErrorId : CmdletInvocationException,Microsoft.PowerShell.Commands.ImportModuleCommand
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The best practices module, a standard module in WIndows can not be loaded by PowerShell 7 as it's not based (yet) on .NET Core. However, it also does not load with WIndows Compatibility module:
The text was updated successfully, but these errors were encountered: