Jeff Hicks makes a connection:
I have a short tip today that you may find useful, especially if you write modules for your private use. I have a number of such modules that I have written to fill my needs. These are private modules that I don’t publish to the PowerShell Gallery. I develop and maintain these modules in
C:\Scripts. This means that when I need to import the module, I have to type the full path.
Read on to see how you can use symbolic links to make this a bit smoother.