Command line arguments from unpackaged form
Forum rules
Do not post any licensing information in this forum.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
Do not post any licensing information in this forum.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
Command line arguments from unpackaged form
Hello, I am trying to pass command line arguments to a powershell form that was created from the new form template in powershell studio. The script has not been packaged. I see from a packaged project you can get the argument from $Commandline variable. Is there a way to get the same command line arguments from a basic unpackaged form? I tried the normal $args[] powershell variable but that does not work.
Re: Command line arguments from unpackaged form
Did you define a parameter block at the top of the script?
PowerShell Code
Double-click the code block to select all.param( $param1, $param2 )David
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
Re: Command line arguments from unpackaged form
I have tried defining in the OnApplicationLoad function without luck.
Re: Command line arguments from unpackaged form
It must be place at the top of the script outside of any function. If you are using PowerShell Studio, it will prompt you for parameters if you place it in the correct location.
David
David
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
Re: Command line arguments from unpackaged form
Sorry, maybe I am doing something wrong but the only way I see to get this at the top of the script is after I export to a powershell file but I don’t see a way to get it to the top of the powershell studio file.
Re: Command line arguments from unpackaged form
If you place the parameter block at the top of the editor you will not have to export the file. PowerShell Studio will move it automatically when you export the script.
I've attached a sample form.
David
I've attached a sample form.
David
- Attachments
-
- ParameterForm.zip
- (1.4 KiB) Downloaded 326 times
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
Re: Command line arguments from unpackaged form
What confuses some people is that the Parm() starement must br the first statement in the file but not necessarily the first line. YOu will find that it is not at teh top of the exported file but is nestaed in after all of the comments.
Here is an example (scroll down to see Parm statement:
The line appears after the end of the recovery block and the generator header but before the header for the generated code. This will pretty much always be the first executable statement.
Here is an example (scroll down to see Parm statement:
Code: Select all
#------------------------------------------------------------------------
# Source File Information (DO NOT MODIFY)
# Source ID: e360d955-555e-4428-a289-0bd6c1ff1e2e
# Source File: C:\Documents and Settings\jvierra\My Documents\SAPIEN\PowerShell Studio 2012\Files\Demo-Databinding.pff
#------------------------------------------------------------------------
#region File Recovery Data (DO NOT MODIFY)
<#RecoveryData:
hhwAAB+LCAAAAAAABADsvQdgHEmWJSYvbcp7f0r1StfgdKEIgGATJNiQQBDswYjN5pLsHWlHIymr
KoHKZVZlXWYWQMztnbz33nvvvffee++997o7nU4n99//P1xmZAFs9s5K2smeIYCqyB8/fnwfPyIe
v8qn1WVeXz/N2uzoN07S9PGXdXFRLLPyWVHmL7JFfvQ0X1Tb+H5SLGfF8mK8Oj9/fLfXjF/GXz+Z
101RLY92x3uP7/ofCPjJT+fTNm2vV/lnH72+btp8Mf4uAa6umvGzql7Iv6M09tUoVVCf7Y938N8o
PVmX7brOP1vm67bOylH6cj0pi+nvlV+/qd7my88mDx5k96f3P919eG8/3zl4+FG6JGQ/++ic4O1+
lE7nRTmrqd1HJ9Wyrauy+YjRJERf1tUqr9trfeF4Os1X7ZN121ZL04ZavcrPc3p/mmuzCTf48vf6
KL1rAN01kAYgn5RFvmxfFz/IPzq6/2B3lO5/ev/Gl0CPJ1U9y+vX7XVJbz4r3uWzp0VWVhc3vvxF
9q5YUH9Pqnf0YlY2+c2vFMv3fQVc8dERE/rGtq/brG5fVk3RFiDvCRGERjat83x547tv8nct4UT9
9JueXhIkbfe8ymbSjj/9/fH347v8u2l+M3O+ymZFJVzws86jNfoShjqp1sSe1yfVLN/EtBHmmufT
tzmN+0297k9Zv/3zaprJHOze2xulnz68xTsy0XFsb/G6cP7uzv4o3du/Rfs32eRsOcuJDz+9XevX
bbW6NQGEm3QE6S2H8FWT/2TRrLOShfFJNn17UpVVPdypz5c6RSfzbHmBmYoT8vcPm3UY965w7v9X
+Jg55r342PHlvU8/kC3x+S1e//ps2dfeN7HZLVH6WWYzYPENs9nzbJKXP+sMVqKX13lJyOSz50XT
Tqp3P5mV6/fksWfU4qOjL4ppXTXVeZu+zpZN+jqvi/NRukvezP1VO0obkP6zJ1U5u8WEedp0h7Tp
/s4t3hG2HRzSLSAI5+7tkiuxd+8W7R3n3orPmXMNaqniljJy2+n2L7xoD/t2+L0Z54ekmoT/4Qno
ON6PY3xrOUrv3V4r9fq9xZsyrQf33ntWb9WaZxUImRm9xUsfpo9oft5GKPH78xcfqngwHvJVf9YZ
qKV+COmNocRGa7b7kPTCbWZIGMf0d4sXVA3cOyCGuY3icQyz9w0IMGbzhzEBpXDNe04AsMjalqLZ
02U2Kb+eg0wafXfnNsZeVbpieosXNBjcf0BKZec2zPG6qtv3GISb6ig2vpgaRc/trfNgxvL7x77+
UNn9oep+hOrvwznHy+kcKu5JRW9TnuJVcTFvb0FyCc1f5Q1h+9HRl7/XLV5xrLZ/sA8tcRsp9u3L
rXoRXntw/73Nym2wEbNyKzzez5gEXBX+cdw0+YI4IG9MW/3k+kg56otsmV3kC+LR8fGaZpGp7Dhr
97acdW93cn7v4P6n2ezep/v5PVIFtqduz4tmWtVlMfkG+HdDLz9LEvMzJ49+3++evXj65Xdf/77W
PR6/OH3z+z6rae6uqvrt73sJ6KSsdh/+vlGhnpXlzYg/rbMr0slfB+Wde+f3zx+c7+7O7u9k97Kv
h7L2fytkHZJ7t0by69AV0O/vPNh7YJC8DXJj5Gt/zjBE57dD8/delD9nWP7eXzy/HZJPi5qUS1Vf
Uyx4WUxzT6Ruj/LX4c8+YbuY3G4AJ1WdO5zvje/fEucumaePfl9SwxeEYIq8fvP7uuy3U7puOP5Q
qFMzCGBzA96OImISnmRNMfUU9M7PKtmdWojiEcHd/mmMzuOXZL/IxtRmaJ/ny5wQ9KyfNIC5dh/e
jX6qH55NdQ0laBp+SpatOM+b9qTO2ajBv+t9ZlufrBuyfuZ7D/bQFy/LrEVC/2gbfqP5w379ar18
/eYYjoH+5l6sriifP8/L0iwGIcbofWhse0itx6/z6bouyFOwayrhC2l34Ym5o7/4JKjU1Ww9bXuN
O59323cnKvbp07yZ1sUqJPLd6Kcn1WKVLa9pca0pLpaURxHhaNJfmC1Wh6mRb5oKbei9ubqu4XT6
89X/7AwrKLQ+18E7/nF0MU9eGP6KMFs4N1/Q8D95fDdY+DMMC5EgBvHXHf+fAAAA//8uMpeKhhwA
AA==#>
#endregion
#========================================================================
# Code Generated By: SAPIEN Technologies, Inc., PowerShell Studio 2012 v3.1.17
# Generated On: 5/1/2013 4:33 PM
# Generated By:
# Organization: Designed Systems & Services
#========================================================================
Param($testvar)
The line appears after the end of the recovery block and the generator header but before the header for the generated code. This will pretty much always be the first executable statement.