Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Rules to check compatibility with PSCore6 #805

Closed
SteveL-MSFT opened this issue Jul 30, 2017 · 1 comment · Fixed by #1133
Closed

Rules to check compatibility with PSCore6 #805

SteveL-MSFT opened this issue Jul 30, 2017 · 1 comment · Fixed by #1133
Labels
Area - Rules Issue - Enhancement

Comments

@SteveL-MSFT
Copy link
Member

Now that PSCore6 has compatibility with many Windows PowerShell .Net modules, we should start developing rules to validate if modules used, .Net api's used, or incompatible Windows PowerShell features (api's removed or changed).
@bergmeister
Copy link
Collaborator

bergmeister commented Mar 30, 2018 •
edited
Loading

@SteveL-MSFT For cmdlets, there is also ready the rule UseCompatibleCmdlets, therefore only the .net apis seem to be missing, maybe the .net core compatibility analyzer could be leveraged for that? PR 954 updates the rule files at least for PSCore 6.0.2

@rjmholt rjmholt mentioned this issue Feb 27, 2019
Merged
11 tasks
@iRon7 iRon7 mentioned this issue Jan 7, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area - Rules Issue - Enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

New PowerShell compatibility rules rjmholt/PSScriptAnalyzer
2 participants
@bergmeister @SteveL-MSFT