Network-Performance-Visualization module not showing when running "get-module -ListAvailable"
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- powershell
- Domain
- networking, tooling
Research direction
Start by reproducing the issue with "get-module -ListAvailable" and inspect the Network-Performance-Visualization module's folder and .psm1 file naming. Done means the module appears in the available-module listing when the folder and .psm1 name match.
Written by the indexing model from the issue text.
Description
Network-Performance-Visualization module not showing when running "get-module -ListAvailable"
this was due to the directory of the .psm1 script not having the same name as the folder that it resided in. I fixed this by only having one folder and naming it the same as the .psm1 file i.e Network-Performance-Visualization
-new to Powershell so may be obvious to some but hope to save some people the headache :)
- Dominant language
- PowerShell
- Stars
- 114
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from Azure/NetworkMonitoring
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
-
Te Open
Difficulty 5/5 Over a week Newbie friendliness 1/100
Azure/NetworkMonitoring#30 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
Azure/NetworkMonitoring#18 ·
-
How Network Topolgy can be used to see network topology diagram for more then one resource group? Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
Azure/NetworkMonitoring#14 ·
All issues in Azure/NetworkMonitoring
Similar issues
-
Browser (wasm) relay client cannot connect to relays whose URL has a trailing-dot FQDN hostname Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
n0-computer/iroh#4550 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
bytecodealliance/rustix#1689 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
home-assistant/supervisor#7248 ·
-
bug cert blocker needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
project-chip/connectedhomeip#74373 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100