Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

FullCLR modules not compatible with PSCore6 #4062

Copy link
Copy link
@SteveL-MSFT

Description

@SteveL-MSFT
Issue body actions

With the change to CoreCLR 2.0 which conforms with .Net Std 2.0 as well as the update to enable searching the GAC for assemblies, we need validation that PSCore6 is a viable replacement for Windows PowerShell 5.x. Please list modules you've tried that do not work here. Vote with 👍 for which modules you most care about to help us prioritize how we work with partners to enable support or have them port to target .Net Std 2.0.

Until #4056 gets resolved, you'll need to manually add Windows PowerShell PSModulePath to discover those modules:

PS > $env:psmodulepath += ";${env:userprofile}\Documents\WindowsPowerShell\Modules;${env:programfiles}\WindowsPowerShell\Modules;${env:windir}\system32\WindowsPowerShell\v1.0\Modules\"

PSSnapins:

  • ActiveDirectory

Failing due to Add-Type

  • RemoteDesktop

Basic tests work:

  • Hyper-V
  • SecureBoot

Needs to be ported:

  • ODataUtils

Not sure:

  • WindowsUpdate (I'm getting error about symsrv.dll also in Windows PowerShell)
Reactions are currently unavailable

Metadata

Metadata

Labels

Issue-Metaan issue used to track multiple issuesan issue used to track multiple issuesResolution-ExternalThe issue is caused by external component(s).The issue is caused by external component(s).WG-Cmdletsgeneral cmdlet issuesgeneral cmdlet issues

Type

No type
No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions

    Morty Proxy This is a proxified and sanitized view of the page, visit original site.