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

Comments

Projects
None yet
1 participant
@johlju
Collaborator

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 added a commit to johlju/xFailOverCluster that referenced this issue Jul 9, 2017

Changes to xCluster
Resolved Script Analyzer rule warnings by changing Get-WmiObject to Get-CimInstance (issue #49).

@johlju johlju referenced this issue Jul 9, 2017

Merged

xCluster: Fixed PSSA rule warnings #110

3 of 5 tasks complete

@johlju johlju added in progress and removed help wanted labels Jul 9, 2017

johlju added a commit to johlju/xFailOverCluster that referenced this issue Jul 14, 2017

Changes to xCluster
Resolved Script Analyzer rule warnings by changing Get-WmiObject to Get-CimInstance (issue #49).

johlju added a commit to johlju/xFailOverCluster that referenced this issue Jul 18, 2017

Changes to xCluster
Resolved Script Analyzer rule warnings by changing Get-WmiObject to Get-CimInstance (issue #49).

@johlju johlju closed this in #110 Jul 21, 2017

johlju added a commit that referenced this issue Jul 21, 2017

xCluster: Fixed PSSA rule warnings (#110)
- Changes to xCluster
  - Resolved Script Analyzer rule warnings by changing Get-WmiObject to
    Get-CimInstance (issue #49).

@johlju johlju removed the in progress label Jul 29, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment