Adding a path doesn't make any difference to finding powershell scripts

  • Thread starter Thread starter BlackJacques
  • Start date Start date
B

BlackJacques

Guest
I've created a Powershell script folder in a certain place, and I'm trying to make it part of my PSModulePath. I've added this to $PROFILE file and also tried this on the command-line but none of the scripts in this folder get seen, unless I explicitly put the full pathname in for them. $env:PSModulePath += ';G:\PIX\Powershell scripts'So what's going wrong here? I've also tried double quotes instead of single quotes. Also tried it with or without the ending backslash.

Continue reading...
 
You must log in or register to reply here.

Similar threads

B
Adding a path doesn't make any difference to finding powershell scripts
Replies
0
Views
10
BlackJacques
B
A
File Explorer: Any way to make full path appear in title bar/copy and paste it?
Replies
0
Views
11
AmyD_112
A
A
File Explorer: Any way to make full path appear in title bar/copy and paste it?
Replies
0
Views
6
AmyD_112
A
A
How to run a Scheduled Task that does not execute if their are spaces in folder path?
Replies
0
Views
63
AdamDoubleYou
A
B
Bios Time and Windows Time Clock can't by Syncronized. Any adjustment to either one shows a difference of 5 hours in the other.
Replies
0
Views
23
BrendanEvanicki
B
Back
Top