cyclops1982 / sourcecode.wizard.powershell Goto Github PK

Some pages have a black title, where it should be green.
The PowerShell Script title could be "Script"

Add the wizard to your process.
Save everything and close the designer
Start the designer.
Right click on the powershell event and select Properties.
An exception occurs.

A powershell script to copy files and update the configurationmanager.config file, would be very helpfull to install the wizard.

The wizard has not been tested on 32bit environments. e
It will not work because of the references pointing to c:\program files x86.

Common feedback on the Scripts page is that people would like add/upload/attach a script.
Another idea is to simply point to a script (add the location of the script).

This would allow scripts to be re-used or to be managed from a separate location, meaning the process does not have to be redeployed if the script fails.

A user has reported that changing a variable from $arg1 to arg1 doesn't seem to work.
The scenario must be tested.

No file reference is added. This causes the process to not compile properly.

Normally, the build on the project does this. Is this step needed for the non-build installation?

You can load snappins in the powershell script itself, but a UI for this would be nice.

Welcome Page:

• There is still a mention of the Advanced Mode, which is not there (yet)
• Change to "This wizard allows you to run a Windows PowerShell script."

Script Page:

• Change to "Specify a PowerShell script by browsing or by typing or pasting in a script. The $K2 variable gives you the K2 process context."

At the moment, you can enter any text you want. The script is not validated.
It would be nice if we could validate if the script is syntax-correct.

When using right click->properties, the property icon looks really bad.

Some people think for us, and add a $ before the variable name. We can simply strip this or put a validation on it.

See title. Assembly info is not updated for new 'release'.