I'm trying to start powershell from within RDM and load a third party module (WASP.dll) - Starting powershell directly from windows CLI, works as its supposed, and i can load the wasp module by using "import-module wasp". The same also works when starting the Powershell RDM Cmdlet from within RDM (also here the "import-module wasp" works.
BUT, If I create a "Powershell (local)" Macro/Script entry, and set's this to run the commandline "powershell -file c:\somepath\myscript\script.ps1" this script fails at the "import-module wasp" command, stating that the module "wasp" was not loaded because no valid module file was found in any module directory.
How come this happen? The script works flawless from outside RDM, and the import-module cmdlet works flawless from within "Powershell RDM Cmdlet" - so why can't RDM execute this powershell and load the module? It's placed in the ordinary powershell module path, and I can't se where else to put this....
What am I doing wrong?
32 vs 64 bit powershell being loaded
The module are registered for a specific bitness
Please verify by checking the "run in 64-bit mode" option in the powershell entry
edited by mcote on 1/28/2015
edited by mcote on 1/28/2015
Maurice
Changing to "run in 64-bit mode" worked as charm! :-)