/build/static/layout/Breadcrumb_cap_w.png

Scripting Question


Admin Script Engine: PowerShell forms defaulting to KixForms

05/19/2014 3874 views

I am trying to create a PowerShell form, this has worked for me in the past selecting PowerShell .Net however this option seems to have been overwritten.  I only have the following choices in the ScriptForm Designer under File/New/PowerShell

  • Windows Native Form
  • KixForms (.net)
  • KixForms (COM)

Under Tools/Designer Options/PowerShell Default Mode I have selected PowerShell .Net Form but it never seems to create this form type.  The resulting scripts does launch and show a form but my code within the click function doesn't seem to do anything.  The same code works outside the form.  Only rework done to the code is to set my variables equal to the .text property of my form fields instead of using Read-Host.

How do I get rid of KixForms?  I don't use Kix.  Has my installation become corrupt?  Thank you.

 

Answer Summary:
0 Comments   [ + ] Show comments

Comments


All Answers

1
KiXforms is a DLL for generating forms (necessary with VBScript and KiXtart). If you are using PowerShell, you can choose "Windows Native Form" and the code will not require any dependencies like the KiXforms DLL. Just be sure you have a PowerShell script open when you launch the Script Form Designer and it should default as expected and when you inject the resulting form code into your script it will be of a supported format. 
Answered 10/30/2014 by: bkelly
Red Belt

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

View more:

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ