PowerShell / PowerShell/PSScriptAnalyzer

Script analyzer warns about unused variables when variable is used in Invoke-Command

Open
#825 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area - PSUseDeclaredVarsMoreThanAssignments
Dominant language
C#
Stars
2.2k
Forks
415
Avg merge
13h 1m
Merged PRs (30d)
2

Description

Hi Guys,

Script Analyzer is flagging a few variables as not used anywhere in the script.

These variables are only used during an Invoke-Command line when is calling them like below

Invoke-Command -Session $S -ScriptBlock {$VMDet = Get-VM $VM}
$VMDetails = Invoke-Command -Session $S -ScriptBlock {$VMDet}

Script analyzer is throwing file: '
message: 'The variable 'VMDet' is assigned but never used. (PSUseDeclaredVarsMoreThanAssignments)'
at: '665,62'
source: 'PSScriptAnalyzer'

Cheers

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the reported PSScriptAnalyzer warning with the Invoke-Command examples in the issue, focusing on how variables inside remote script blocks are analyzed. Trace the variable-use analysis from that diagnostic and determine what behavior should count as a use; done means the false unused-variable warning no longer appears for this pattern.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.