Import/Create with Custom Types

This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
This topic is 8 years and 4 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.
User avatar
kmkirkpatrick
Posts: 4
Last visit: Thu Jul 19, 2018 7:23 pm

Import/Create with Custom Types

Post by kmkirkpatrick »

When creating a new help file and importing from an existing module that has custom .NET types I get two errors. In this particular case, I have cmdlets in the module that specify .NET Types that get loaded as part of VMware's PowerCLI PSSnapIn.

The first error I get looks like this:
Error 1
Error 1
pshw_error1.PNG (35.45 KiB) Viewed 21531 times
The second error is just a blank window:
Error 2
Error 2
pshw_error2.PNG (31.85 KiB) Viewed 21531 times
After clicking through these, the import process hangs and I have to cancel out.

It appears that since the PowerCLI .NET types get loaded just-in-time, PSHW is not aware of them?

Any help is much appreciated.

Platform
---------------------
PSHW Version: 1.0.15
OS: Windows 7 x64
PS Version: 5.0.10514.6
Installed Sapien Products: PS Studio 2015, WMI Explorer 2015, Productivity Pack 2015
User avatar
SAPIEN Support Forums
Posts: 945
Last visit: Thu Oct 22, 2015 1:10 pm

Import/Create with Custom Types

Post by SAPIEN Support Forums »

This is an automated post. A real person will respond soon.

Thank you for posting, kmkirkpatrick.

Did you remember to include the following?
  • 1. Product, version and build (e.g. Product: PowerShell Help Writer 2015, Version & Build: 1.0.9. Version and build information can be found in the product's About box accessed by clicking the blue icon with the 'i' in the upper right hand corner of the ribbon.)
    2. Specify if you are running a 32 or 64 bit version
    3. Specify your operating system and if it is 32 or 64 bit.
    4. Attach a screenshot if your issue can be seen on the screen
    5. Attach a zip file if you have multiple files (crash reports, log entries, etc.) related to your issue.
If not, please take a moment to edit your original post or reply to this one.

*** Make sure you do not post any licensing information ***
User avatar
juneblender
Posts: 93
Last visit: Thu Mar 30, 2017 8:54 am

Re: Import/Create with Custom Types

Post by juneblender »

When you run Get-Command -Module <ModuleName> on the cmdlets/functions in your module, are the results accurate? In particular, the command syntax and parameter attributes?
User avatar
kmkirkpatrick
Posts: 4
Last visit: Thu Jul 19, 2018 7:23 pm

Re: Import/Create with Custom Types

Post by kmkirkpatrick »

June,

It works when I have the PowerCLI PSSnapin loaded, but errors if I have not loaded the PSSnapin, which is what I expected.
User avatar
juneblender
Posts: 93
Last visit: Thu Mar 30, 2017 8:54 am

Re: Import/Create with Custom Types

Post by juneblender »

That makes sense. Since 3.0, PowerShell is optimized for managing modules, but the optimizations, like module auto-loading, don't affect snap-ins.

Let's see if David comes up with a solution for your help file.
User avatar
davidc
Posts: 5913
Last visit: Mon Jul 08, 2019 8:55 am
Been upvoted: 2 times

Re: Import/Create with Custom Types

Post by davidc »

We are attempting to recreate the issue.

David
David
SAPIEN Technologies, Inc.
This topic is 8 years and 4 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.