Can't load powershell module from explicit path

Question

I can't recall if this stopped working at some point or has always been this way. When I develop powershell modules I would like to be able to load them explicitly from my local repo directory to make sure everything is working properly. MSDN indicates this should work, however I get the error:

"The specified module .\SomeModule was not loaded because no valid module file was found in any module directory. FileNotFoundException"

I would expect this is because it can't find the psm1 file in the directory but I can't understand why. I can load the module by referencing the psm1 file directly but this excludes anything being loaded by the manifest. I can also copy the module to one of the standard module paths and it will load correctly. This is what I've been doing as a work around but I'd love to get this figured out. TIA

**Update: Ran process monitor while running the import command. Interesting results. Seems like it may just be a powershell bug.

You can load a module by referencing the module manifest file directly. — Mark Wragg
– Mark Wragg, Commented Mar 23, 2017 at 14:00
Ahh, that did work. I thought I tried that before but I wonder if I hadn't specified the psm1 file in the RootModule property yet. I'll check that and the ModuleList to see what effect it has on things loading properly like that. If no one else has anything to say about loading it using the folder path as shown on msdn I'll mark you answer as correct. It suits my needs just fine. Thanks! — Mike Frank
– Mike Frank ♦, Commented Mar 23, 2017 at 14:06
Is the module manifest (.psd1) filename the same as the folder? eg ...\MyModule\MyModule.psd1? If they aren't the same then you have to explicitly reference the manifest filename when loading the module. If they match then you can just provide the folder path without manifest filename. — henrycarteruk
– henrycarteruk, Commented Mar 23, 2017 at 14:36
@JamesC. They are named the same. Definitely strange behavior. — Mike Frank
– Mike Frank ♦, Commented Mar 24, 2017 at 2:11

Mark Wragg · Accepted Answer · 2017-03-23 14:08:13Z

1

You can load the module by referencing the module manifest file (.psd1) directly, which will then ensure any dependencies are loaded.

answered Mar 23, 2017 at 14:08

Mark Wragg

23.6k7 gold badges48 silver badges77 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Can't load powershell module from explicit path

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related