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.

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

xCluster: Script Analyzer warnings that need to be fixed #49

Closed
johlju opened this issue Jun 13, 2017 · 0 comments · Fixed by #110
Closed

xCluster: Script Analyzer warnings that need to be fixed #49

johlju opened this issue Jun 13, 2017 · 0 comments · Fixed by #110
Labels
enhancement The issue is an enhancement request.

Comments

@johlju
Copy link
Member

johlju commented Jun 13, 2017

The following PSScriptAnalyzer errors need to be fixed:
MSFT_xCluster.psm1 (Line 25): $null should be on the left side of equality comparisons.
MSFT_xCluster.psm1 (Line 25): $null should be on the left side of equality comparisons.
MSFT_xCluster.psm1 (Line 81): $null should be on the left side of equality comparisons.
MSFT_xCluster.psm1 (Line 81): $null should be on the left side of equality comparisons.
MSFT_xCluster.psm1 (Line 186): $null should be on the left side of equality comparisons.
MSFT_xCluster.psm1 (Line 186): $null should be on the left side of equality comparisons.
MSFT_xCluster.psm1 (Line 24): File 'MSFT_xCluster.psm1' uses WMI cmdlet. For PowerShell 3.0 and above, use CIM cmdlet which perform the same tasks as the WMI cmdlets. The CIM cmdlets comply with WS-Management (WSMan) standards and with the Common Information Model (CIM) standard, which enables the cmdlets to use the same techniques to manage Windows computers and those running other operating systems.
MSFT_xCluster.psm1 (Line 80): File 'MSFT_xCluster.psm1' uses WMI cmdlet. For PowerShell 3.0 and above, use CIM cmdlet which perform the same tasks as the WMI cmdlets. The CIM cmdlets comply with WS-Management (WSMan) standards and with the Common Information Model (CIM) standard, which enables the cmdlets to use the same techniques to manage Windows computers and those running other operating systems.
MSFT_xCluster.psm1 (Line 185): File 'MSFT_xCluster.psm1' uses WMI cmdlet. For PowerShell 3.0 and above, use CIM cmdlet which perform the same tasks as the WMI cmdlets. The CIM cmdlets comply with WS-Management (WSMan) standards and with the Common Information Model (CIM) standard, which enables the cmdlets to use the same techniques to manage Windows computers and those running other operating systems.

@johlju johlju added enhancement The issue is an enhancement request. help wanted The issue is up for grabs for anyone in the community. labels Jun 13, 2017
johlju added a commit to johlju/FailoverClusterDsc that referenced this issue Jul 9, 2017
Resolved Script Analyzer rule warnings by changing Get-WmiObject to Get-CimInstance (issue dsccommunity#49).
@johlju johlju added in progress The issue is being actively worked on by someone. and removed help wanted The issue is up for grabs for anyone in the community. labels Jul 9, 2017
johlju added a commit to johlju/FailoverClusterDsc that referenced this issue Jul 14, 2017
Resolved Script Analyzer rule warnings by changing Get-WmiObject to Get-CimInstance (issue dsccommunity#49).
johlju added a commit to johlju/FailoverClusterDsc that referenced this issue Jul 18, 2017
Resolved Script Analyzer rule warnings by changing Get-WmiObject to Get-CimInstance (issue dsccommunity#49).
johlju added a commit that referenced this issue Jul 21, 2017
- Changes to xCluster
  - Resolved Script Analyzer rule warnings by changing Get-WmiObject to
    Get-CimInstance (issue #49).
@johlju johlju removed the in progress The issue is being actively worked on by someone. label Jul 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement The issue is an enhancement request.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant