Product, version and build: PowerShell Studio 2016 v5.2.127
32 or 64 bit version of product: 64
Operating system: W7
32 or 64 bit OS: 64
PowerShell Version: 5.0
The same modules and snapins that allow the "not found" types to work in the console are present in the Object Browser. PrimalSense on commands works, help works...only the types are having issues. I've tried rebuilding the cache; no change.
I hate those red exclamation marks. I'd also like to be able to browse the types in the .NET Object Browser.
Thanks!
Types not recognizes for VMware modules/snapins
Forum rules
Do not post any licensing information in this forum.
Do not post any licensing information in this forum.
Re: Types not recognizes for VMware modules/snapins
This would actually be a feature request as we don't cache the types found in modules. I'll go ahead and move this topic to the Wishlist and Feature Request forum so that we can get this added to our list.
DevinL
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
Re: Types not recognizes for VMware modules/snapins
[TOPIC MOVED TO WISHLIST AND FEATURE REQUESTS FORUM BY MODERATOR]
DevinL
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
Re: Types not recognizes for VMware modules/snapins
The exclamations are syntax errors reported by PowerShell engine directly and not produced by us.
In order to get PrimalSense for types, you will have to load the assemblies by the following methods:
1. Reference the assembly using Ribbon->Edit->Assemblies:
Then press the Add button and then Browse for the assembly:
Note: This will not persist on a ps1 file.
2. Alternatively, use an Add-Type statement and the PrimalSense will automatically load the assembly type information:
You can comment the line out when you need to save and run the script.
In order to get PrimalSense for types, you will have to load the assemblies by the following methods:
1. Reference the assembly using Ribbon->Edit->Assemblies:
Then press the Add button and then Browse for the assembly:
Note: This will not persist on a ps1 file.
2. Alternatively, use an Add-Type statement and the PrimalSense will automatically load the assembly type information:
- Add-Type -Path C:\...\Assembly.dll
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.