Types not recognizes for VMware modules/snapins

Post feature requests, product enhancement ideas, and other product-specific suggestions here. Do not post bug reports.
Forum rules
Do not post any licensing information in this forum.
This topic is 7 years and 7 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
Locked
User avatar
brinkcm
Posts: 25
Last visit: Mon Mar 09, 2020 6:18 am

Types not recognizes for VMware modules/snapins

Post by brinkcm »

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!
Bug1.png
Bug1.png (33.97 KiB) Viewed 3379 times
DevinL
Posts: 1098
Last visit: Tue Jun 06, 2017 9:15 am

Re: Types not recognizes for VMware modules/snapins

Post by DevinL »

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.
DevinL
Posts: 1098
Last visit: Tue Jun 06, 2017 9:15 am

Re: Types not recognizes for VMware modules/snapins

Post by DevinL »

[TOPIC MOVED TO WISHLIST AND FEATURE REQUESTS FORUM BY MODERATOR]
DevinL
SAPIEN Technologies, Inc.
User avatar
davidc
Posts: 5913
Last visit: Mon Jul 08, 2019 8:55 am
Been upvoted: 2 times

Re: Types not recognizes for VMware modules/snapins

Post by davidc »

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:
Edit Assemblies.png
Edit Assemblies.png (9.46 KiB) Viewed 3364 times
Then press the Add button and then Browse for the assembly:
Add Assembly - Browse.png
Add Assembly - Browse.png (53.13 KiB) Viewed 3364 times
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:
  1. Add-Type -Path C:\...\Assembly.dll
You can comment the line out when you need to save and run the script.
David
SAPIEN Technologies, Inc.
This topic is 7 years and 7 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
Locked