Custom Modules and Object Browser

Post by **FarmersDairy** » Fri Mar 15, 2013 5:52 am

I am having a problem getting my custom modules so that I can use them from the object browser in PowerShell Studio 2012. I have the modules in their own directors in "C:\Users\username\Documents\WindowsPowerShell\Modules", When I press the refresh button in the object browser one of two things happen. Either the module does not appear in the list or it appears, but it is "EMPTY". I have tried this on two different systems with the same results.

Post by **davidc** » Fri Mar 15, 2013 9:54 am

Usually when it’s empty it means it didn't find an exported function or there is an error that prevents the cache from building. This could happen when the module requires a specific host or has a dependency that can't load.

If this is not the case, please zip and email the problem module to support@sapien.com and we will take a look at it.

David

Post by **FarmersDairy** » Tue Mar 19, 2013 9:17 am

Thanks David. I have forwarded the information.

Post by **davidc** » Tue Mar 19, 2013 9:58 am

Found the problem. In the manifest you need to specify the RootModule:

RootModule = 'AmberLabOS.psm1'

Once you add this line the module commands will show.

David

Post by **FarmersDairy** » Tue Mar 19, 2013 1:08 pm

Thanks for the response, but no joy.

I added the line (copy & paste) from your post, saved it, restarted PS Studio (to be safe) and then did a refresh in the Object Browser. I am doing this on my work (Windows 8 Pro) system. I will try it at home (Windows 7 Pro) system again, as I have the same problem there.

I will note that when I originally created the module, I used NEW | NEW MODULE PROJECT in PS Studio. I just created a new test module and it does not automatically include a RootModule entry in the generated manifest file. Bug?

Post by **davidc** » Tue Mar 19, 2013 1:42 pm

It is included automatically. I saw that you commented out a few fields in the manifest and it is possible that you removed the entry. A simple test is to create a new module and copy the functions over. To test the module run the following in the console:

PowerShell Code

Double-click the code block to select all.

Import-Module AmberLabOS
Get-Command -Module AmberLabOS

David

Post by **FarmersDairy** » Wed Mar 20, 2013 5:35 am

As I said in my last post, I did create a new module. I did exactly as you suggested and copy/pasted the code. I did not touch the manifest file. I got the same result and no "RootModule" line.

Post by **FarmersDairy** » Wed Mar 20, 2013 8:59 am

I created another module from scratch and once again I got the same results on my Windows 8 Pro system. I did not get a chance to try it on my Windows 7 Pro system at home. I will try this evening and post the results.

Post by **FarmersDairy** » Wed Mar 20, 2013 9:20 am

Dumb, dumb, dumb, DUMB!!!

Execution Policy was set to AllSigned instead of RemoteSigned. It still does not explain why the ROOTMODULE was missing in the manifest, though. It still is not there, but the modules work now and appear in the Object Browser.

Thanks for you help, David. Tough dealing with dumb people is it not?

Post by **davidc** » Wed Mar 20, 2013 9:30 am

Sorry it wasn't RootModule, which is what you had commented out in your original psd1 file. It is actually ModuleToProcess.

Either way I’m glad it is finally working.

David

SAPIEN Technologies