PowerShell / PowerShell/PSScriptAnalyzer
System.InvalidOperationException from Invoke-ScriptAnalyzer command when debugging PSES
Open
Nobody has claimed this yet.
Issue - Concurrency
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
I've been debugging other issues in PSES and I'm seeing multiple instances of this exception. Can this be safely ignored or is there a problem here:
This was using Windows PowerShell 5.1 on Windows 10 FCU.
Copied over from PSES - https://github.com/PowerShell/PowerShellEditorServices/issues/572
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Invoke-ScriptAnalyzer command while debugging PSES, using Windows PowerShell 5.1 on Windows 10 as reported. Compare the repeated InvalidOperationException with the related PowerShellEditorServices issue to determine whether it can be ignored or indicates a real problem.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100