SAPIEN Forums

Product, version and build:
64 bit version of product: PowerShell Studio 2016 5.2.127
Operating system: Windows 10 64-bit 10.0.14393 (aks 1607)
PowerShell Version: 5.1.14393

To use PS16 with the AWS cmdlets, must I install the _entire_ .Net SDK from AWS? (http://sdk-for-net.amazonwebservices.co ... ForNet.msi)

With PowerShell 5, I'd prefer to install-module -name awspowershell -repository psgallery. But if I remove the .Net SDK and then do that, PS16 doesn't understand any AWS cmdlets.

Today, for example, the .Net download installed 3.1.92.0 of the AWS cmdlets; psgallery offers 3.1.93.0. AWS is clearly moving to "prefer" psgallery installation. The Windows PS ISE has no trouble with the psgallery installation. Why does PS16?

I was able to use the AWS cmdlets just fine on my test machine here. I fired up the VM, installed SPS 5.2.127 and ran Install-Module -Name AWSPowerShell.

After installing the module I refreshed the cache and when it completed the AWSPowerShell module was in the Object Browser[1] and the cmdlets appeared in the PrimalSense window as expected[2].

Did you happen to rebuild the cache after installing the AWSPowerShell module? You can do this by pressing the Rebuild Cache button in the ribbon[3].

[1] [2] [3]

Did you uninstall any AWS SDKs from Windows control panel and install ONLY the PowerShell Gallery module?

When I do that -- and rebuild PSS16's cache -- I get the results shown in the attached screens snippet. The PowerShell console is fine. PSS 16 has no idea what the AWS cmdlets are.

I didn't have to uninstall any AWS SDK's as there were none installed. I only ran Install-Module -Name AWSPowerShell from a fresh virtual machine and rebuilt the cache in PowerShell Studio. After trying this again, I opened the Uninstall a Program window to verify no AWS SDK's were installed alongside the module and there was nothing there:

Have you tried removing all references to the AWS module, including the AWS .NET SDK, and only running the Install-Module cmdlet?

DevinL wrote:Have you tried removing all references to the AWS module, including the AWS .NET SDK, and only running the Install-Module cmdlet?

Marco...polo. That is precisely the question I started this thread with, If I uninstall the downloadable AWS .NET SDK and then install just the cmdlets from PS Gallery, it doesn't work.

I must have misread your initial post where you mentioned installing the module then removing the .NET SDK.

I'll look into this more thoroughly and get back when I have some more information.

Let's try enabling the module using our Cache Editor which basically forces the module to appear in the Object Browser and PrimalSense. Follow these steps to accomplish this:

1. Click Cache Editor in the ribbon
2. Check the box next to AWSPowerShell
3. Click Build
4. Click Close
5. Verify the module is in the Object Browser panel

Right after posting that, I noticed in your screenshot the \\Mac\Home\Documents\PowerShell path. Are you doing any of this using remote connections as opposed to all on one local machine?